So exciting
http://www.androidpolice.com/2012/0...rnel-source-code-including-that-of-the-one-v/
EDIT: http://dl4.htc.com/RomCode/Source_and_Binaries/doubleshot-gb-crc-2.6.35-f3a1982.tar.gz
Sent from my DoubleShot Lite using Tapatalk 2
ac3theone said:
so exciting
http://www.androidpolice.com/2012/0...rnel-source-code-including-that-of-the-one-v/
sent from my doubleshot lite using tapatalk 2
Click to expand...
Click to collapse
yyyyyyyyyyeeeeeeeeeeeeeeeeeeeeeessssssssssssssssssssssssss
Soo.... Does anyone think we could see some pure AOSP action now? Or someone could update the kernel for CM7? As you will see in general someone -whom I suspect is not alone - would love an AOSP ROM on our HTC Doubleshot.
Maybe this kernel isn't that good as we suppose...
Nusferatu said:
Maybe this kernel isn't that good as we suppose...
Click to expand...
Click to collapse
Well.... What did u expect? we don't have an ICS ROM in our future that we have been made aware of, and it is truly great news as this is something that has made many a dev stray away from this device - now we might be able to get CM7 stable - and others to work off of CM7 such as blahblah
Good news nevertheless
We need to get CM7 STABLE ASAP
We may be late in the running, but that doesn't mean we still can't get merged into the main tree
Nusferatu said:
Maybe this kernel isn't that good as we suppose...
Click to expand...
Click to collapse
Its worse than you thought... The source code was released a really long time ago. This is just an updated kernel, so the real reason for lack of development isn't because the source code wasn't available. :/
michaelmab88 said:
Its worse than you thought... The source code was released a really long time ago. This is just an updated kernel, so the real reason for lack of development isn't because the source code wasn't available. :/
Click to expand...
Click to collapse
Updated source is awesome though. Tried to get it earlier and couldn't - can't on shift and will be working straight until Friday afternoon so won't have a chance to try again for a few days.
Any percieved lack of development is due to people not putting any effort into it - everyone who cries about a lack of development should do something about it instead of waiting for someone else to do so.
Why come here if you don't want to get into dev, worse, come here and complain about yourself not doing anything? Kinda silly.
Whenever I see people complain about a lack of development I wonder why they would basically make fun of themselves? It gives me a laugh at their expense...
Sent from a digital distance.
Yeah i just got the source downloaded because it matches the new ota I'm running now, I've never seen what a dual core source looks like, or if I'll even be able to compile a kernel for this device, I've only compiled a few for the EVO shift, which was straight forward with a little help from my boy drob...who knows o may get it to boot ha-ha.......nope I fudged something in my toolchain It's broke....again.....LOL
Sent from my myTouch_4G_Slide using Tapatalk 2
strapped365 said:
Yeah i just got the source downloaded because it matches the new ota I'm running now, I've never seen what a dual core source looks like, or if I'll even be able to compile a kernel for this device, I've only compiled a few for the EVO shift, which was straight forward with a little help from my boy drob...who knows o may get it to boot ha-ha
Sent from my myTouch_4G_Slide using Tapatalk 2
Click to expand...
Click to collapse
http://dl.dropbox.com/u/62701184/arm-eabi-4.4.3.zip
That link is for the toolchain you need, i've been hosting it on dropbox for a while until I get it over to a more permanent host.
I can walk you through it later if you want.
I have it written up on how to set up your linux environment and make changes, including versioning instructions, just haven't found the time to polish off a part of it and add it to the dev reference yet.
Got a whole space reserved for the how to from start to finish on making kernels for the doubleshot, and i've already walked people through it with no kernel dev experience so if you've done it for another device it'll be a cakewalk.
I'm eating breakfast now and gotta run out to another job, and going straight from there to dodgeball practice, then work again tonight and from there right to the job i'm about to do again tomorrow this time, so tomorrow night i'm doubtless going to sleep - maybe as early as saturday evening I could go through it with you on IRC if you are interested.
Otherwise I hope to have that in the dev ref next week, work permitting.
Blue6IX said:
http://dl.dropbox.com/u/62701184/arm-eabi-4.4.3.zip
That link is for the toolchain you need, i've been hosting it on dropbox for a while until I get it over to a more permanent host.
I can walk you through it later if you want.
I have it written up on how to set up your linux environment and make changes, including versioning instructions, just haven't found the time to polish off a part of it and add it to the dev reference yet.
Got a whole space reserved for the how to from start to finish on making kernels for the doubleshot, and i've already walked people through it with no kernel dev experience so if you've done it for another device it'll be a cakewalk.
I'm eating breakfast now and gotta run out to another job, and going straight from there to dodgeball practice, then work again tonight and from there right to the job i'm about to do again tomorrow this time, so tomorrow night i'm doubtless going to sleep - maybe as early as saturday evening I could go through it with you on IRC if you are interested.
Otherwise I hope to have that in the dev ref next week, work permitting.
Click to expand...
Click to collapse
I might have my little one on Saturday night so that maybe a no go for then, the tool chain I currently have is 4.4.1, because anything newer for the speedy breaks a ton during the compile.....I changed some commands around for ****s and giggles and got a zimage in arch/arm/boot so I split it with the ota ramdisk and I'm just gonna try....if that goes south I'll setup your tool chain....thanks blue your like the DoubleShot dictionary....
Also I'm gonna grab one of your kernel zips for test flashes if that's ok
Sent from my myTouch_4G_Slide using Tapatalk 2
Blue6IX said:
Updated source is awesome though. Tried to get it earlier and couldn't - can't on shift and will be working straight until Friday afternoon so won't have a chance to try again for a few days.
Any percieved lack of development is due to people not putting any effort into it - everyone who cries about a lack of development should do something about it instead of waiting for someone else to do so.
Why come here if you don't want to get into dev, worse, come here and complain about yourself not doing anything? Kinda silly.
Whenever I see people complain about a lack of development I wonder why they would basically make fun of themselves? It gives me a laugh at their expense...
Sent from a digital distance.
Click to expand...
Click to collapse
Hey I'm not complaining, and I am working on it! I just have to balance between school and work and learning how to build cm7/cm9 from source.
You can check out a little bit of what I've been working on github.com/mafischer
michaelmab88 said:
Hey I'm not complaining, and I am working on it! I just have to balance between school and work and learning how to build cm7/cm9 from source.
You can check out a little bit of what I've been working on github.com/mafischer
Click to expand...
Click to collapse
Lol no worries my friend, was a general comment and not aimed at you in particular, just a perspective I wanted to put out there and you were the first opportunity to do so.
I still haven't found the time to get git set up and learn how to use it - that whole life getting in the way of living thing. Given you have git going that makes you a more responsible dev then I in my book -
@ strapped: all my work available is a contribution to the open source community at large, and the members of XDA in particular. If any of it can be useful, especially as a teaching tool, I wholeheartedly encourage it!
Sent from a digital distance.
Where did all of you come from?
Never knew there was this many people working on the Doubleshot in the background...
gtmaster303 said:
Where did all of you come from?
Never knew there was this many people working on the Doubleshot in the background...
Click to expand...
Click to collapse
I've been here since i preordered my doubleshot... I just haven't had time to work on much of anything, so there's no point in advertising to the community that I'm gonna work on things that may or may not ever get finished. I don't want to spread false hope or anything.
I am however, graduating in may; I'm going to be working over at walmart isd for a summer internship, and I should have more time on my hands once school is over!
How integrated is the Sense stuff into the kernel? As I understand it, we've had trouble removing the Sense underpinnings from the operating system to get it working with things such as Sixaxis. I'm aware that this is entirely a lack of understanding on my part.
I would quite love to get involved in building a ROM myself, perhaps even setting up CM9 from scratch. I just have no idea how to get started. I've mucked around with custom kernels and embedded linux (not android) devices in the past, but I'm not sure how that knowledge would apply to this system. I also have no history of proper programming languages or anything like that. I'm vaguely familiar with how to compile things with the ARM toolchains.
I'm also a tad nervous about bricking the device by writing to a memory location that I really shouldn't be touching.
Kanerix said:
How integrated is the Sense stuff into the kernel? As I understand it, we've had trouble removing the Sense underpinnings from the operating system to get it working with things such as Sixaxis. I'm aware that this is entirely a lack of understanding on my part.
I would quite love to get involved in building a ROM myself, perhaps even setting up CM9 from scratch. I just have no idea how to get started. I've mucked around with custom kernels and embedded linux (not android) devices in the past, but I'm not sure how that knowledge would apply to this system. I also have no history of proper programming languages or anything like that. I'm vaguely familiar with how to compile things with the ARM toolchains.
I'm also a tad nervous about bricking the device by writing to a memory location that I really shouldn't be touching.
Click to expand...
Click to collapse
Sorry for quoting the whole post just to address one thing, but in regards to sixaxis I'm sure it's a safe bet that if one were to simply replace the stock bluetooth stack with the one kornyone used for cm7 in my bulletproof rom it would work fine, and I doubt much other, if any modification would be necessary.
I haven't had time to try, and truthfully i'd rather build my own so am kinda intentionally not trying - I am more interested in the project then just jumping into a solution.
It really depends on what you are trying to do - some sense things can be replaced with relatively little effort, other things are so interwoven it would take considerable effort and time to unravel, reverse engineer and implement a new solution.
A lot of people have been working on different parts of unravelling sense since back in august, and around the middle of that month we got s-off and really started digging in.
There is a considerable knowledge base lurking here to address this kind of stuff if people make it known they are working on things - dig back through the history of the device here at XDA and you can catch a glimpse of it and get some direction on who you can approach when you hit a roadblock, depending on what kind of roadblock it is.
It's better for us as a community to have that kind of knowledge out on the public forum, but there's much more here then what face value suggests.
I've been trying to get that kind of stuff and a general 'start here' knowledge base built in the developers reference stickied here in dev, reading through that would be a good place to start getting oriented on devving for the dubleshot.
I just go through some crazy work cycles and sometimes can't be around much for a time here and ther, so my contributions come in groups and gaps.
Sent from a digital distance.
michaelmab88 said:
I've been here since i preordered my doubleshot... I just haven't had time to work on much of anything, so there's no point in advertising to the community that I'm gonna work on things that may or may not ever get finished. I don't want to spread false hope or anything.
I am however, graduating in may; I'm going to be working over at walmart isd for a summer internship, and I should have more time on my hands once school is over!
Click to expand...
Click to collapse
It doesn't matter whether or not you finish. Status updates would be nice though. At least that way people can know what you're up to, and they may even be able to help you and vice versa.
No one here is demanding an ETA or even a completion at all. We're all in for the fun of it.
Either way I think I can safely speak for everyone when I say, we're excited to see what you got cooking
Blue6IX said:
Sorry for quoting the whole post just to address one thing, but in regards to sixaxis I'm sure it's a safe bet that if one were to simply replace the stock bluetooth stack with the one kornyone used for cm7 in my bulletproof rom it would work fine, and I doubt much other, if any modification would be necessary.
I haven't had time to try, and truthfully i'd rather build my own so am kinda intentionally not trying - I am more interested in the project then just jumping into a solution.
It really depends on what you are trying to do - some sense things can be replaced with relatively little effort, other things are so interwoven it would take considerable effort and time to unravel, reverse engineer and implement a new solution.
A lot of people have been working on different parts of unravelling sense since back in august, and around the middle of that month we got s-off and really started digging in.
There is a considerable knowledge base lurking here to address this kind of stuff if people make it known they are working on things - dig back through the history of the device here at XDA and you can catch a glimpse of it and get some direction on who you can approach when you hit a roadblock, depending on what kind of roadblock it is.
It's better for us as a community to have that kind of knowledge out on the public forum, but there's much more here then what face value suggests.
I've been trying to get that kind of stuff and a general 'start here' knowledge base built in the developers reference stickied here in dev, reading through that would be a good place to start getting oriented on devving for the dubleshot.
I just go through some crazy work cycles and sometimes can't be around much for a time here and ther, so my contributions come in groups and gaps.
Sent from a digital distance.
Click to expand...
Click to collapse
I've been trying to go through the dev reference that you posted and track down as much scattered information as I can, but I'm still not quite sure what I'm doing. Alas.
Regarding bluetooth: would the gingerbread stack be compatible with ICS?
gtmaster303 said:
It doesn't matter whether or not you finish. Status updates would be nice though. At least that way people can know what you're up to, and they may even be able to help you and vice versa.
No one here is demanding an ETA or even a completion at all. We're all in for the fun of it.
Either way I think I can safely speak for everyone when I say, we're excited to see what you got cooking
Click to expand...
Click to collapse
Well what I'm currently up to is making a stable version of cm7 for the doubleshot. I have made lots of progress as far as learning all the tools necessary to compile android from source, which is a relatively simple task. The not so simple part is trying to put together like a puzzle, the source code from other devices. I've hit some roadblocks and I'm currently asking some devs for help, but while I'm at it I guess I can ask for help here on xda.
michaelmab88 said:
Well what I'm currently up to is making a stable version of cm7 for the doubleshot.
Click to expand...
Click to collapse
Yeehaaa!
Related
I understand that the sdk is nowhere near full featured, but now there are system dumps of the xoom, maybe helpful, right?
Well, i have never ported nor built a ROM before (done some theming and have no problem learning code). I came across these 2 port how-tos:
http://forum.xda-developers.com/showpost.php?p=11546129&postcount=76
http://android-dls.com/wiki/index.php?title=HOWTO:_Unpack,_Edit,_and_Re-Pack_Boot_Images
Is that all i really need to get HC to boot? The instructions seem extensive but not impossible or difficult.
Has anyone attempted this or gotten HC to boot on the g-tablet? I'm willing to take a crack at it if a dev could tell me whether i'm on the right track with the tutorials or do i need more knowledge.
When it comes to ROM building/porting, i gotta start somewhere. I've been around these forums for years and its about time I attempt to return the favor (hopefully without bricking my device lol)
Thanks in advance.
If this post needs to be moved, i'm sorry mods, but i figured this is strictly a development question.
Feel free to attempt it. There are people working on it and have come to the conclusion that source is needed plus a couple files from nvidia.
IMO porting the sdk is a complete waste of time tho. You would be much better starting off with a rom that will compile like froyo rather than starting with something that doesnt work yet
thebadfrog said:
Feel free to attempt it. There are people working on it and have come to the conclusion that source is needed plus a couple files from nvidia.
IMO porting the sdk is a complete waste of time tho. You would be much better starting off with a rom that will compile like froyo rather than starting with something that doesnt work yet
Click to expand...
Click to collapse
thanks for the insight. You're right, maybe froyo would be a good place to start so i could get used to the process on something that will compile. I'll probably give it shot in the next couple of days.
jump on the irc channel. freenode channel #tegratab. Lots of help and a willingness to help those that want to learn. I've compiled cm7 several times myself. Not my cup of tea but it was interesting.
Moved Here
Also a notice to the Admins, Mods, and various users at this site:
My personal email address is not to be used to mock, insult, or otherwise argue points made on this forum. The comments made here, despite how offensive they may be interpreted, do not hold a serious tone. If you feel it necessary to send things to my personal address, please have spine to use your own return address. Please respect the fact that I do not invade your personal life by keeping my comments restricted to this site, and I only request I am granted the same common decency.
Wow, haven't seen you in a long time. Thank you for giving this a shot! : )
RjsShadows said:
Wow, haven't seen you in a long time. Thank you for giving this a shot! : )
Click to expand...
Click to collapse
It seems that in some alternate reality it is acceptable to assume that "in your spare time" means cancel all of your plans and get used to fluorescent lighting because daylight is just the glare on your computer screen. Either way, I am downloading some 2 gigs of random ICS stuff and finally received my replacement Macbook, so between projects I will try to get something moving on this.
You rock! Subscribing.
Right now all I have is the sdk version from RootzWiki, which appears was a post of just the modified boot. I have a few Nexus4g builds that claim to work. I have a rebuilt boot image and I am trying to pack all of it together and see what happens so I know where to start.
Sent from my ADR6400L using Tapatalk
twistedumbrella said:
Right now all I have is the sdk version from RootzWiki, which appears was a post and abandon build. I have a few Nexus4g builds that claim to work. I have a rebuilt boot image and I am trying to pack all of it together and see what happens so I know where to start.
Sent from my ADR6400L using Tapatalk
Click to expand...
Click to collapse
Sick, i'm really looking forward to this. Don't overwork yourself though
twistedumbrella said:
Right now all I have is the sdk version from RootzWiki, which appears was a post and abandon build. I have a few Nexus4g builds that claim to work. I have a rebuilt boot image and I am trying to pack all of it together and see what happens so I know where to start.
Sent from my ADR6400L using Tapatalk
Click to expand...
Click to collapse
i am guessing these first ports will be very alpha due to no real software from google to work with?
Thread cleaned (and it's only a few hours old).
If you have nothing useful to say, DON'T bother posting...
the_scotsman said:
Thread cleaned (and it's only a few hours old).
If you have nothing useful to say, DON'T bother posting...
Click to expand...
Click to collapse
What did I miss? Did the angry beavers try to build another dam? I fell asleep waiting for the new mac to migrate from the old one. Now that everything is moved over I can actually load up what I have and at least move a little closer to posting actual files to play with.
Sent from my ADR6400L using Tapatalk
Real deal? Did source drop and only for you? Cause otherwise this is just another non-working SDK port.
doug piston said:
Real deal? Did source drop and only for you? Cause otherwise this is just another non-working SDK port.
Click to expand...
Click to collapse
I guess if you didn't see the previous thread, which was more or less a rick-roll youtube video that said it isn't possible to get anything running, then an understandable first reaction is to make rude comments...
But if you read the thread you are responding to, you would have seen that on the Nexus it is a working build, capable of being used as more than just a proof-of-concept. Then again, I don't expect people to read these days because they are too busy writing...
http://forum.xda-developers.com/showthread.php?t=1313337
http://forums.androidcentral.com/sprint-nexus-s-4g-rooting-roms-hacks/127806-rom-ics-sdk-port-wip.html
Best leave the developing to the developers and stop back when there is something to load up and complain about
So getting an SDK port working on a Nexus S is the same as getting it to run on the ThunderBolt?
I'm not saying it isn't possible though I highly doubt it will work. I'm saying don't call it the "Real Deal".
doug piston said:
So getting an SDK port working on a Nexus S is the same as getting it to run on the ThunderBolt?
I'm not saying it isn't possible though I highly doubt it will work. I'm saying don't call it the "Real Deal".
Click to expand...
Click to collapse
This is real ICS development, and not a prank so it is as the title says "ICS Development (Real Deal)"
And no, getting a port working on the Nexus S is not the same as getting it to work on the Thunderbolt, which is why there isn't a file in that first post yet. I think you are assuming that the only thing available is the SDK image, though, when the full system dump is out there also.
My previous statement still stands.. Why don't you go shake down some kids for their script source, and come back when there is something here to test.
thatdudebutch said:
Posting threads with no content seems ridiculous. Why not work on the port rather than type sentence after sentence of nonsense in here. Just saying.
Click to expand...
Click to collapse
You do know downloads, packing, transferring, uploading, etc do run in the background right? I remember back when threads like this rallied up support and assistance instead of whatever you call what you're doing... For the record I am waiting on a data wipe and a lot of stuff is still installing since the computer only came yesterday.
I can just toss up every little edit I test and brick phones all day long, or I can document the process and release when it hits milestones. That way I can catch input along the way and prevent a lot of wasted time.
Just swapped the boot on the posted Nexus build, changed over all the apn info, and added in all the keylayout and hardware files. Going through and finding everything that needs to be swapped for a straight port, then if it runs I will post up the progress.
Sent from my ADR6400L using Tapatalk
twistedumbrella said:
You do know downloads, packing, transferring, uploading, etc do run in the background right? I remember back when threads like this rallied up support and assistance instead of whatever you call what you're doing... For the record I am waiting on a data wipe and a lot of stuff is still installing since the computer only came yesterday.
Click to expand...
Click to collapse
Whether you get anywhere or not, good luck
Nothing wrong with doing something just for the challenge of having said you did it and the experience.
I am glad to see someone putting some real effort into getting an ICS port going. And appreciate you posting your progress here along the way. I'm interested in seeing how you get where you get.
Good Luck
As already mentioned, this thread is for relevant discussion of the upcoming port.
If you have nothing constructive to contribute then keep it to yourself.
No *****ing and whining about the probable lack of functionality, no pestering for ETA's and no petty personal playground nonsense.
No more warningsIf this goes off topic again then there will be repercussions.
conantroutman said:
As already mentioned, this thread is for relevant discussion of the upcoming port.
If you have nothing constructive to contribute then keep it to yourself.
No *****ing and whining about the probably lack of functionality, no pestering for ETA's and no petty personal playground nonsense.
No more warningsIf this goes off topic again then there will be repercussions.
Click to expand...
Click to collapse
Thanks. The good news is that I have a shopping list of what has been changed to go from sdk to working port. The bad news is that I also have a project due Thursday that I need to actually spend some time with.
For anyone with the sdk build, make sure before even trying to run it that you replace all the /system/bin files that just say toolbox with real files or set up symlinks for them. Busybox also needs to be added/replaced in /system/xbin
This will get that version to where you can run logcat and see the EGL errors, but it will also be in a condition to start tweaking files to get the touchscreen running.
Sent from my ADR6400L using Tapatalk
I can't waaaaiiiitttt!!
Take as much time as you need! Your life is more important than this.
I am uploading what I have, but not because it is a huge step forward. I fixed all the commands and added the files that should fix the touchscreen, but didn't on this device.
This is still a step forward from the base build we currently have. At least typing a command no longer results in "toolbox" being displayed instead of results. I reverted everything I tested to make sure the only test changes were absolutely necessary to provide a solid base. I will post a link as soon as it is up.
Sent from my ADR6400L using Tapatalk
As you all know, nearly two weeks ago the long awaited source code for the Android Gingerbread software was released. This had been a joyous occasion for many of us who had been patiently awaiting its release in hopes that it would lead to working versions of Cyanogenmod and MIUI on our phones, as well as several kernel modifications that were not previously possible. The first few hours of speculation turned into days, which turned into weeks, with the promises of development yet to be fulfilled. As it turns out the fears of some of you had come true, that the few developers that were left lost interest in the Galaxy S 4G for other projects.
While people like Raver have actively stuck with us, there has been a dead silence by those who were previously the most visible on this forum. Whitehawkx who has left us for the Galaxy S2, Dsexton who had left for lack of a separate computer,and Dr Honk who God knows where he is. Krylon ive seen mention working on a kernel once but with little detail. These were some of the best we had and we need to make it overwhelmingly obvious to them that they are wanted and needed here. So I propose that we take the time to let them know that the source code they've wanted and needed is now available and ready to be worked. Youre welcome to write up your own words for a message, though heres something I threw together along with the public contact info for the devs.
Feel free to reach out to any other devs who have not been listed here or from other forums.
Update: Dev's emails were removed by site mods. If you would like to email the people below, you can readily find their email in their user profiles and in their Donate To Me links.
Whitehawkx:
[URL]http://forum.xda-developers.com/private.php?do=newpm&u=3051621[/URL]
http://forum.xda-developers.com/sendmessage.php?do=mailmember&u=3051621
Dr Honk:
http://forum.xda-developers.com/private.php?do=newpm&u=2785735
Dsexton702:
http://forum.xda-developers.com/private.php?do=newpm&u=3954931
“Hello (dev screen name),
This is (your screen name) from the Galaxy S 4G forums on XDA. If you haven’t heard, the source code for Gingerbread we have been eagerly awaiting was finally released a few weeks ago for our phones. With the source finally released, the limitations our devs had faced before in developing for the SGS4G are now gone, and the path is clear for development of CM7 and MIUI for our phones. I have noticed you have not been around the SGS4G forums recently, but I along with all the other forum members have been hopefully awaiting your return to developing for our phones with the expertise you have shown in all of your many other projects for the SGS4G. As well, the lack of devs on the forum have left many of the still poplar ROM’s unmaintained and not updated to the latest official release. Please come back to developing for the SGS4G for all of us who have spent hours testing and using your ROM’s and show us what your talents can turn these phones into.
Thank you”
I think this is good intended but i fear it wont change anything.
Dont forget soma and airfluip who has been developing for our phones recently.
Krylin said in twitter that he will begin working in a ROM based on GB for our phones. Although he said he will start it today if he doesnt its still good news. I know he can make kernels and roms. Also raver is working. Dsexton said he will get a computer soon and that he needed break. White.... I dont know he droppwd when ki3 leaked. But oh well, lets enjoy or wait.
I've been lurking these forums since this phone came out, with the occasional post here and there.
I have seen people waiting months just for root.
I remember kb5 enhanced was our only ROM for times without end, just to have that developer throw a fit at Mr.Clown for mistakingly closing his thread and leave us hanging.
I remember following Krylon on twitter for what seemed like an eternity, until we finally had cwm on our phones.
Then came the good times.
New roms coming out just about every week, themes, mods, and all the goodies we see on our forums today.
New developers popping up, the formation of teams like aerodonk and acid.
Now we are back in one of these silent periods.
It seems like all development stopped.
But one thing I've learned from these forums is that patience is a virtue.
We go from bad times to good times, to bad again, and so on.
I'm sure there is progress being done right now.
No matter how little, our how long it's taking, it will come.
And a new life cycle will start for our phones.
We just gotta hang tight, get through this metamorphose, and then our phone will come out, greater then before!
Saw on krylons twitter something about doing another rom based off of the gb update so that looks promising.
Also its not just the sgs4g. I own a sensation as well and things have really slowed there too.
I understand everybodys frustration with the length of time that it is taking for us to get new roms. But you have to understand these guys do this in their spare time. And yes, it is true that because of Samsung and t mobile taking forever to release a GB for us made some of the devs loose interest and move to other devices; however, we still have Raver and Krylon on or side, Dsexton will be coming back soon, and hopefully we can get Drhonk and Whitehawx back if not for developing but for at least guidance, tips, and support. I for one have started trying to learn how to do some of this but without a Linux machine it is a bit difficult. But there is no reason some of you can't chip in and try to learn this stuff too. Not to override the few true devs we have, but to assist them.
Sent from my SGH-T959V using XDA App
Hi Thomas
Please share your knowledge source. I am willing to learn as well, though to tell you the truth, moding and theming couldn't care me less, I'm always into performance and reliability, as well as good RTL and foreign language support (like in CM and MIUI).
Other than that, I'm always on stock theme.
I'm no dev, but I'm considering to become one in the future.
Sent from me
itzik2sh said:
Hi Thomas
Please share your knowledge source. I am willing to learn as well, though to tell you the truth, moding and theming couldn't care me less, I'm always into performance and reliability, as well as good RTL and foreign language support (like in CM and MIUI).
Other than that, I'm always on stock theme.
I'm no dev, but I'm considering to become one in the future.
Sent from me
Click to expand...
Click to collapse
My biggest resources are picking the brain of RaverX3X and google. You can do most everything on a windows machine except mod kernels and make an Odin .tar (for those you need Linux or the ability to run Linux in a vm environment). There are quite a few tutorials out there. You just have to download the right tools to do it, have lots of spare time to devote to it and the gonads to test it.lol... Pm me later with specific questions and I can give you direct links to tutorials that might help you as well.
Sent from my SGH-T959V using XDA App
i say we make a donation pool. Whoever gives us cm7 or miui first gets the money.
Sent from my SGH-T959V using xda premium
josepresas said:
i say we make a donation pool. Whoever gives us cm7 or miui first gets the money.
Sent from my SGH-T959V using xda premium
Click to expand...
Click to collapse
Might not be such a bad idea.
josepresas said:
i say we make a donation pool. Whoever gives us cm7 or miui first gets the money.
Sent from my SGH-T959V using xda premium
Click to expand...
Click to collapse
Might want to add the disclaimer it should be officially supported
josepresas said:
i say we make a donation pool. Whoever gives us cm7 or miui first gets the money.
Click to expand...
Click to collapse
Interesting idea. The only issue I see is what if we collect money and no one steps up to the plate. Would everyone just get a refund or would the money go towards another cause?
thomas.raines said:
My biggest resources are picking the brain of RaverX3X and google. You can do most everything on a windows machine except mod kernels and make an Odin .tar (for those you need Linux or the ability to run Linux in a vm environment). There are quite a few tutorials out there. You just have to download the right tools to do it, have lots of spare time to devote to it and the gonads to test it.lol... Pm me later with specific questions and I can give you direct links to tutorials that might help you as well.
Sent from my SGH-T959V using XDA App
Click to expand...
Click to collapse
You don't necessarily need Linux in order to make an Odin flashable tar file, I personally use Cygwin to make the modem packages.
Yes I am aware that Cygwin is Linux-like command line, but it is by no means Linux in a VM environment.
ultimakillz said:
Interesting idea. The only issue I see is what if we collect money and no one steps up to the plate. Would everyone just get a refund or would the money go towards another cause?
Click to expand...
Click to collapse
I would rather set a bounty for ICS. CM9 would be a better goal in my opinion.
what happened to CM8? did i miss something?
candler33w said:
I would rather set a bounty for ICS. CM9 would be a better goal in my opinion.
Click to expand...
Click to collapse
Well yea, a fund to get us any of the major ROMs cm9 miui or ICS etc..
And idk what we would do with the money if no one delivers.. ideas?
Sent from my SGH-T959V using xda premium
I remember when i had the galaxy vibrant early this year i was so into the device cause they were a lots of roms here to choose from and thats one of my concerns now for this device now. If you go to the vibrant section there are a lots of 2.2 biulds 2.2.1, 2.3 ,2.3.3 etc etc etc. And they are all different. Including from stock to MIUI and htc Sence. As well as gingerbread and honeycomb. So my question is why the devs didnt work on some builds like those for this device. From my end i really dont care about what number of the OS is as long the build is stable, fast, bloatware free, custom ringtones, wallpapers, and other great thing that i did manage to see on my old vibrant that i no longer own :/
Yesterday my older sister got the galaxy s 2 for tmobile and its so awsome. I have envy in me now jajajajaja xD
josepresas said:
Well yea, a fund to get us any of the major ROMs cm9 miui or ICS etc..
And idk what we would do with the money if no one delivers.. ideas?
Sent from my SGH-T959V using xda premium
Click to expand...
Click to collapse
I would leave it as a standing bounty like they did with the HP Touchpad. Someone will jump on it if its large enough.
---------- Post added at 08:29 PM ---------- Previous post was at 08:28 PM ----------
jager555 said:
what happened to CM8? did i miss something?
Click to expand...
Click to collapse
CM8 was reserved for Honeycomb so ICS will be CM9
crackpot said:
You don't necessarily need Linux in order to make an Odin flashable tar file, I personally use Cygwin to make the modem packages.
Yes I am aware that Cygwin is Linux-like command line, but it is by no means Linux in a VM environment.
Click to expand...
Click to collapse
This is true. Which is what I am learning to use now, but I forgot to add that part... Thanks for catching my error. From my understanding, you can use it to modify a kernel as well, but i'm not having very good luck with it yet.
Sent from my SGH-T959V using XDA App
thomas.raines said:
This is true. Which is what I am learning to use now, but I forgot to add that part... Thanks for catching my error. From my understanding, you can use it to modify a kernel as well, but i'm not having very good luck with it yet.
Sent from my SGH-T959V using XDA App
Click to expand...
Click to collapse
This is mere conjecture on my part, but I would assume that you can modify the kernel in Windows as long as your text editor supports Unix-type line endings (Notepad++ works nicely), and then compile it using presumably gcc in Cygwin. Again, this is merely speculation on my part, having only built a Linux kernel on Linux, for my desktop.
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
I really want to learn how Android works. I want to be able to build Android from source, and compile Roms. The goodies. But anytime I try, it's end up horribly. I just want to know where to start! Should I make a stock based Rom, and learn how to tweak it out? Should I buy a certain book, or read some threads! I don't know Xo I really want to become a Dev. Android is my life, and I want to be able to do what Strapped, XMC, and Tbalden do. Any tips are good tips.
I sure do wish you all the luck in the world Agent. And you certainly want to fashion yourself after three mighty fine developers too. I've had some of those same desires myself after seeing what someone that knows their stuff can do. I had so much trouble with HS Spanish and a few AutoCad Lisp routines that I can't even imagine biting off C++ or some of the other programming languages!
My youngest son though.....now that's a completely different story. :good:
WeekendsR2Short said:
I sure do wish you all the luck in the world Agent. And you certainly want to fashion yourself after three mighty fine developers too. I've had some of those same desires myself after seeing what someone that knows their stuff can do. I had so much trouble with HS Spanish and a few AutoCad Lisp routines that I can't even imagine biting off C++ or some of the other programming languages!
My youngest son though.....now that's a completely different story. :good:
Click to expand...
Click to collapse
I wanna learn while I'm still young, I'm out of school for the time being. I really want to take advantage of these couple Months before life is all about business, and how to properly Manage/Own a T-Mobile.
Sent from my myTouch_4G_Slide using Tapatalk 2
NOW is the time my friend before life gets in the way of your youth and ambitions. It WILL distract you and before you know it spare time will seem like it never comes often enough. I admire ALL of you that persue what interests you and learn while that mind is still fresh. KWIM?
WeekendsR2Short said:
NOW is the time my friend before life gets in the way of your youth and ambitions. It WILL distract you and before you know it spare time will seem like it never comes often enough. I admire ALL of you that persue what interests you and learn while that mind is still fresh. KWIM?
Click to expand...
Click to collapse
Hell Yeah, I'm considering taking classes at the local community college for Java. Apparently it's useful for learning Android. I go to a strictly business college. So I can't learn anything related to Android.
Sent from my myTouch_4G_Slide using Tapatalk 2
OK, so I have an Idea. I want to do what CM said, and learn the basic. I'm going to use Undeads Sense 3.0 Port as a base, and theme it to Sense 4.0. Remove the Bulletproof settings, and push over another tweak app. I want to make it as fast as possible, and have great battery. I always felt Sense 3.0 was the smoothest Sense rom we ever got. Zero Hickups, and No Lag. I'm going to at least do it on a personal level. Try to get a hold of Undead (he's IP Banned on XDA & Rootz), but it may be hard. Maybe even try and get the Amaze Camera Mod working. Just simple, basic things. Once I get used to the waters, I'll try something bigger. Like Paranoid Android.
I just found an Interesting guide about porting any Sense rom, to any Sense Phone. Pssshh, could you image Sense 2.1 on our phone. That would be sweet. The guide is boosted to be made for the most simplest of minds. So I feel I can take extreme advantage of it.
Sent from my myTouch_4G_Slide using Tapatalk 2
Keep on plugging - I admire your determination. And please keep letting us know how you're getting on - the start of a journey.
Sent from my myTouch_4G_Slide using xda premium
Alright agent since I can't quote your last post, I was on the inc2 forums and they have a wifi issue that's solved by turning the always on data off
Sent from my HTC MyTouch 4G Slide running MikXE
Where is Blue when you need him?
::Respect::
Hey guys!
I would say that making a post or thread like this is really the first step - knowledge can be gained, but the passion, that drive to work through all the tedious testing, retesting, writing and re-writing is not something that can be taught.
So start small.
We all have grand designs, plans and ideas - heck there's so much this device is capable of that I want it to do, starting everything at once just leads to unfinished projects and fragmented learning.
If you bring that excitement, that hunger for knowledge, then the rest falls into place but it takes time.
"I never let school interfere with my education"
...is such a fantastic quote. It's up to you to choose to take the time to sit down and read a technical document, white-paper or tutorial while your friends are out wasting time.
Definitely make time to walk away and socialize with real people, but remember that learning how to do this stuff takes a lot of time, effort and tons of frustration and dead ends.
I've been playing with software code for near 20 years now, and I still consider myself not much past amatuer status.
...and status means literally nothing. The only two things that matter are what you know, and what you don't.
So don't lie to yourself. Don't pretend to know something just because you are afraid of what people will think if they find out you don't. It's okay to say "I don't know"
In fact, it's essential to be able to say that not only to yourself, but to be able to admit that to the community, your friends, whomever.
If you don't, then you have no place to start learning. Pretending to know something just prevents you from actually being able to start learning how to do it.
So, after you are comfortable with a truthful assessment of what you can and can't do, the next step is to figure out how to go about learning what you don't know.
The biggest mistake everyone makes is taking on a huge project because that's what the end goal is.
"A journey of a thousand miles begins with a single step"
...another good one!
I'm sure we've all heard it before, but haven't pondered it so deeply. Another way to say it might be:
"The making of an awesome ROM begins with changing a single icon"
Break down the project you want to do into the smallest possible steps.
Can you decompile an app?
If not, definitely learn how to do that.
Once you have it decompiled, browse all the code. Especially what you don't understand or makes no sense. Don't try to understand it all, just absorb it and get to know what it looks like.
Now do that with every app on your device (play with all the stock apps first - they all came from the same place and reflect a certain coding style)
Now that you've browsed through all the code of all your stock apps, do it again. ...and again ...and again ... and again.
Sick of it yet? It's been a few weeks now and you've learned nothing you can directly use.
This part always separates the people serious about doing it from the ones turned off by all the tedious work with nothing concrete to show for it.
I mean, you've spent a couple of weeks just looking at code with no idea what you are looking at.
What you don't immediately notice is that you start to get a sense of the pattern, the layout, and what things are the same, similar, and completely different.
Now you start looking at tutorials you've read in the past and go 'wow, I know kinda what that means, I saw something like that in the code here!'
Ah - now it begins!
When it gets to be too much, do something you can handle from start to finish.
Change an icon, tweak the color of a font, something simple, but that you can feel the pride of success and accomplishment in.
Can you compile an app?
Decompile a working app - change nothing - then recompile it. Install it on your device.
Does it still work? Probably not.
Why?
Ah - the question that drives us.
9 times out of 10 someone releasing something cool is not because they wanted to make it, but because they wanted to learn how to make it.
One thing people forget all the time is that the stock software on the device is built by teams of people with delegated tasks and diverse talents that TOGETHER contribute to the success of the final product.
You? You're alone. You have to do it all. Graphics, sound, coding, planning, research, testing - you are taking a project that requires untold hours of dedication from a team of people ... Maybe just on the graphics alone. A whole other team is working on sound, another team is working on code, there is management to structure goals and delegate tasks.
Managers who may have no technical ability but a good handle on how to keep everyone moving and workikng cohesively. Other management that is keeping the teams on point with each other.
...and it still takes them lots of time to get things done. Not because it's some bloated over-staffed group with too much red tape (though that does happen) - but more because there is simply so much to do.
The next time I spend 40+ hours behind the keyboard with maybe not even a bathroom break won't be the first nor the last. I've sat down to do something on Friday and had someone stop by on Sunday night and I'm still in my work clothes from my day shift Friday, didn't even realize Saturday came and gone.
Does it all require that level of dedication - no, but, you get lost in it and that can happen. Never force myself to do it, just get caught up in learning it all.
Don't expect too much from yourself. You absolutely have the community behind you and so much knowledge here, tons of people willing to help, but in the end it's up to you.
You to do graphics.
You to do sound.
You to write the code.
You to compile it all.
You to figure out why it doesn't work ( and it rarely does).
For every success, you have many, many failures to get there. Especially starting out. Expect to get it wrong. Expect it to be broke just because you touched it. If it isn't, honestly, you're doing it wrong.
We learn so much less from success then we do from failure. If you aren't failing you aren't learning. If it always works the first time, then you are just doing the same tired stuff you always have.
You wanna learn how to code for Android?
Read everything you can, absorb the forums, go download source and browse it. Decompile all your apps and browse them. Start looking up what you don't know.
For every one thing you do learn, you realize there are ten new things you never knew you didn't know.
Now go learn about them, because each one of them will lead you to something else, or many something elses that you didn't even realize you didn't know.
...and did I mention put lots of time into ignoring what you want to do, and learning how to do it one tiny little piece ata time?
Patience is most important.
The patience to only change one variable, recompile, test, test, and test some more. Then, when you are satisfied with the result of one minor little change, make one more tiny change and repeat the process.
Learn the scientific method, and follow it rigorously. If you don't, might as well not bother getting into this stuff because all you will do is get frustrated.
You have to work slowly, patiently, one small step at a time. Try to predict the result of the tiny change you made, and then see if it was what you thought or a surprise. Why was it a surprise?
The question of why is the only thing that matters. Every one of those you answer is one more weapon at your disposal for the battle, one more tool in your box, one more pencil on your desk.
If you have little to no coding experience and expect to sit down and whip out a ROM, you are only setting yourself up for failure. But one day you can, with hard work, lots and lots of time, uncountable failures and hours of frustration and coding something just to have it not even compile, let alone work.
Have you taken the time to map the device?
When you got it stock, you should have put a file browser on it ( root explorer - just buy it already, you need it) and browsed the entire device.
Take a notebook and write out a full device tree on paper, everything you can see. Every folder, every file or folder in them, sizes, permissions, any detail you can see.
Why? Because it already works. You are lookoing at how a working ROM is structured.
I mean, how can you make something if you don't know what it is, looks like, how it acts?
Learned ADB and fastboot yet? Why not? You wonNt be successful if you don't.
This is a pretty long list already - and we've barely scratched the surface. A ROM is not a Sunday afternoon project - a ROM is a dedicated months and months long never ending project that eats up more time then you have every day.
So I'll leave you with one last thing before I go make a thread that people aren't gonna want to see - but I'm not leaving you guys, far from it.
Learn algebra, learn it well, or don't bother attempting to write code. (Or work in any construction trades/build anything professionally.)
Algebra is the single most important learned skill one can pick up across just about anything you can ever do with your life, and absolutely vital in computing.
There really is no "go here, learn this" method - you need to aquire the skills necessary to succeed in your project.
So go break something (minor - don't brick your phone) and then learn how to fix it. ...and pay attention in math class.
Sent from a digital distance.
Blue6IX said:
Huge Epic Post.
Click to expand...
Click to collapse
It's like your a warlock and when I typed your name, POOF! :victory:
This post covers every aspect you could ask for, I'm sure Agent isn't the only one who will gain knowledge from this post, thanks Blue!:highfive:
CoNsPiRiSiZe said:
It's like your a warlock and when I typed your name, POOF! :victory:
This post covers every aspect you could ask for, I'm sure Agent isn't the only one who will gain knowledge from this post, thanks Blue!:highfive:
Click to expand...
Click to collapse
Hell. Yeah. I'm just going to start theming. I want to make the ICS messaging Icon blue, and a blacked out UI.
Sent from my HTC MyTouch 4G Slide using Tapatalk 2
I just got ubuntu on my computer, spent an hour trying to install java lol. Now to figure out why adb doesn't work the way it does in windows haha.
edit: finally got adb working. i have no idea what i did, but after installing a bunch of different libs, time to start exploring haha =D
ekoee said:
I just got ubuntu on my computer, spent an hour trying to install java lol. Now to figure out why adb doesn't work the way it does in windows haha.
edit: finally got adb working. i have no idea what i did, but after installing a bunch of different libs, time to start exploring haha =D
Click to expand...
Click to collapse
Java was a b***h when I installed an unsupported version for compiling. This is helpful though it will guide you through installing and it can even switch java versions if you don't like your current one
AgentCherryColla said:
Hell. Yeah. I'm just going to start theming. I want to make the ICS messaging Icon blue, and a blacked out UI.
Sent from my HTC MyTouch 4G Slide using Tapatalk 2
Click to expand...
Click to collapse
I saw this done on AOKP website as a mod, i think this plus built in messaging pop up like an MIUI thing would b beast
::Respect::
ekoee said:
I just got ubuntu on my computer, spent an hour trying to install java lol. Now to figure out why adb doesn't work the way it does in windows haha.
edit: finally got adb working. i have no idea what i did, but after installing a bunch of different libs, time to start exploring haha =D
Click to expand...
Click to collapse
Man, i'll tell ya - if you had to pick the one thing someone would do to take a step into learning to bend android to your will, installing linux is the best reply possible.
Windows is great to get your feet wet, and can manage some things more easily - frilly stuff, eye candy type details.
If you want to talk about experiencing the thrilling joys of success all that invested effort brings - doing so on a linux box is so much more rewarding then on a windows box.
Definitely see about getting a second monitor if you can swing it. Working with two display panels more then doubles your productivity. You can have a tutorial on one screen and be following along on the other.
That aside, one reason the linux box is so much more rewarding is because of the range of things you can mess with.
You can't work with a kernel in windows. Already right there the most important part of the ROM is off limits to you in a windows box. (as I sit here typing this on windows - mind you.)
Another reason linux is so sweet to work on for coding android is that they speak the same language. Writing code is quicker and easier, connecting the device happens more seamlessly and swiftly.
All these little things add up to save you time.
...and time is your greatest hindrance. It slips by all too quickly and then you are obligated to walk away and do something else. So being able to squeeze more work into less time is the consistent refinement of what you know.
Rarely do you learn how to do something the most efficient way on your own, and really that is the heart of open source. You can see how someone else did something, and learn from how they got there.
I've communicated with people I couldn't speak the language of through code, sending changes back and forth without any written correspondence.
To be able to explain the various joys and experiences learning computer coding has brought me would be impossible. There is so much intangible awesomeness that comes from investing time into learning all of this.
Especially since cell phones are so popular and mobile computing is so easy any more. Being able to bend the device in your hand precisely to your will is ever becoming a more important skill to have.
For those wanting to invest that time into what brings us all here collectively, the rewards really are beyond what you would think starting out.
As much as I wanna delv into this as ACC, I simply have no time haha. However, learning this now will probably help me in the future, so why not.
At the very least I'll finally know what you guys are talking about in the dev section lol.
Blue6IX said:
Another reason linux is so sweet to work on for coding android is that they speak the same language. Writing code is quicker and easier, connecting the device happens more seamlessly and swiftly.
Click to expand...
Click to collapse
This. Install Linux, learn to love it, and learn to customize it. A big part of setting linux up the way you want involves working in a command line, troubleshooting when errors come up, building, and compiling. The time you spend troubleshooting and customizing everything on your linux box will familiarize you with all the commands, shortcuts, quirks, and understanding of why this does that in a linux environment, and will help you to no end.
I'm going to get a new Laptop before school starts up again. Then I can finally get cracking