Database Info

[Q] Help Needed developing newest battery tweak

Collin_ph here. I've been working for literally months trying to get my battery tweak on the android market. The problem is that I don't do front end java development.. or should I say, I never have done it before. I have 2 full time jobs as a developer and a business owner and really don't have time to learn another language and framework. I'd LOVE to work with someone who A. is Experienced, and B. Has the time to work on something like this.
The next version really is going to be great, I just think it's time to get it on the marketplace so it's compatible with more than just certain ROMS on the Hero. I know it's technically possible.. I know the ins and outs of making it work, I'm just way behind on making a pure android app. If anyone really really wants to help, let me know. I'm wanting to make a profitable app on the market, and I want someone who'll share in the vision and the profits. There'll always be a free version, especially for XDA users. If you're interested, please PM me. This will make 3 times I'll be starting over because developers don't really have time to work on the project. If you're like me, you know this has potential.

Let's do it

collin_ph, will there be a shell script version of new battery tweak too, yes?
i think shell script is efficient and stable enough for me and i don't want to install an android java app.
love your tweak!!

collin_ph said:
Collin_ph here. I've been working for literally months trying to get my battery tweak on the android market. The problem is that I don't do front end java development.. or should I say, I never have done it before. I have 2 full time jobs as a developer and a business owner and really don't have time to learn another language and framework. I'd LOVE to work with someone who A. is Experienced, and B. Has the time to work on something like this.
The next version really is going to be great, I just think it's time to get it on the marketplace so it's compatible with more than just certain ROMS on the Hero. I know it's technically possible.. I know the ins and outs of making it work, I'm just way behind on making a pure android app. If anyone really really wants to help, let me know. I'm wanting to make a profitable app on the market, and I want someone who'll share in the vision and the profits. There'll always be a free version, especially for XDA users. If you're interested, please PM me. This will make 3 times I'll be starting over because developers don't really have time to work on the project. If you're like me, you know this has potential.
Click to expand...
Click to collapse
jasonmaloney said:
Let's do it
Click to expand...
Click to collapse
LOL, with JM throwing his hat in the ring, you KNOW you're gonna have a winner!
A huge thanks to both of you guys!

In the long run, I really don't have any plans to continue the shell version. There are a lot of misconceptions about the shell version-- a lot of people think that there is no process that continues running, however, there is. I have a plan to have a very similar setup with the java version that should still have a small cpu and memory footprint.. possibly even smaller CPU usage as the Java version can be event based rather than timer based. Anyway, just know that I will do whatever possible to make the program fulfill its need the best and most efficient way possible. With Java, we can be usable on more than just a hero without having to port it every time, we can run on different roms without porting, we'll be able to run more things event based and remove most of the timer based things (if not all), and lastly, we'll be able to do things that we weren't able to do in shell. I'm excited for the new version, but as always, it's job is to make the phone faster and give it better battery performance. The new version will most likely be called "tweak tool", as Battery optimization will be only one of its functions, but the most important.
Anyway, after Easter, I'll be sitting down and going over a plan for the new version (once more). Hopefully we'll get a full blown launch out of this attempt.

collin_ph said:
With Java, we can be usable on more than just a hero without having to port it every time
Click to expand...
Click to collapse
I say Hooah!!

Haha. I'm excitied. Hopefully you two will join together. This is gonna be outstanding! Ha. Yea I know I'll shut up.

I'll have to learn how to write Android apps. Already know Java.
Can't be that hard after modifying Android source, right?

jasonmaloney said:
I'll have to learn how to write Android apps. Already know Java.
Can't be that hard after modifying Android source, right?
Click to expand...
Click to collapse
If you set up Eclipse, there is a lot of help/examples available. App Inventor is another tool that might be an option, perhaps less flexibility, but a "block" oriented approach that does a lot of the work for you.

jaybob413 said:
If you set up Eclipse, there is a lot of help/examples available. App Inventor is another tool that might be an option, perhaps less flexibility, but a "block" oriented approach that does a lot of the work for you.
Click to expand...
Click to collapse
I've tried appinventor and as a developer, it feels totally bass ackwards. I'm no java developer, but I've already put together a couple of tests in eclipse, which is the direction I want to go-- especially since I'll be doing everything in my power to make sure it's optimized.

jasonmaloney said:
I'll have to learn how to write Android apps. Already know Java.
Can't be that hard after modifying Android source, right?
Click to expand...
Click to collapse
Holy crap, if you AND jaybob are going to help collin_ph, this app is as good as gold. You two are by far two of the most dedicated and steadfast devs I've ever known on XDA.
Excited to see what comes out of this, happily willing to buy any app that comes out of it as support

KERNEL source released

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!

KitKat for HTC Thunderbolt

With Kitkat being ported to so many older devices because of the lowered system requirements, I figured its time we get one on the ThunderBolt. I by no means can do this on my own, so that is why I am starting this thread. I will try to reach out to as many devs as possible to get this going. Just a little about myself, Ive done basic ROM developement on a few devices, the most notable being the 2 generations of the Nexus 7. Over the past few months I have greatly expanded my knowledge and capabilities with android. The extent of my coding knowledge is basic Java, a little bit of C++, and arduino, which is why I need help for this. I see this as both a learning opportunity for me as well as a chance to participate in expanding the Thunderbolt dev community. I'm mainly looking for somone who can help with kernel and radio develpement, and someone who can help with porting the actual software over. The reason I need these people is because I have no experience in kernel development, and as for the actual developement of a KitKat rom, I'm sure its more complex then downloading KitKat source and throwing in the Thunderbolt device trees. I've been researching the topic and havent found much useful information. If you feel you can help support the effort please contact me.
Email: [email protected]
Developers willing to contribute:
(will add as people offer)

frap129 said:
With Kitkat being ported to so many older devices because of the lowered system requirements, I figured its time we get one on the ThunderBolt. I by no means can do this on my own, so that is why I am starting this thread. I will try to reach out to as many devs as possible to get this going. Just a little about myself, Ive done basic ROM developement on a few devices, the most notable being the 2 generations of the Nexus 7. Over the past few months I have greatly expanded my knowledge and capabilities with android. The extent of my coding knowledge is basic Java, a little bit of C++, and arduino, which is why I need help for this. I see this as both a learning opportunity for me as well as a chance to participate in expanding the Thunderbolt dev community. I'm mainly looking for somone who can help with kernel and radio develpement, and someone who can help with porting the actual software over. The reason I need these people is because I have no experience in kernel development, and as for the actual developement of a KitKat rom, I'm sure its more complex then downloading KitKat source and throwing in the Thunderbolt device trees. I've been researching the topic and havent found much useful information. If you feel you can help support the effort please contact me.
Email: [email protected]
Developers willing to contribute:
(will add as people offer)
Click to expand...
Click to collapse
im waiting for a long time,thank you a lot!!!!!!!!!!!!!!!!!!!!!!!!
you can also try to transplant from msm8655 device，thats easier than bulid it.

chongbos said:
im waiting for a long time,thank you a lot!!!!!!!!!!!!!!!!!!!!!!!!
you can also try to transplant from msm8655 device，thats easier than bulid it.
Click to expand...
Click to collapse
I assume by transplant you mean just try to flash a rom for another device with simmilar specs? (Same MSM8655 CPU, Same amount of ram, etc)

Kitkat would be awesome!
I'll test whatever you throw up here.
That's about all I'm good for. Sorry.

you can try contact santod here, but need register
http://forums.infectedrom.com/forumdisplay.php/79-Thunderbolt-Android-Development
He's last man standing Thunderbolt expert developer...
but i hear He already switch to HTC One project n leave Thunderbolt.
it very exciting news if can be true:good:

Ive contacted a few members who have experience with either porting or the thunderbolt, none of wich have responded as of yet.

her you can try :
http://forum.xda-developers.com/member.php?u=4310221
http://forum.xda-developers.com/member.php?u=4471805
http://forum.xda-developers.com/member.php?u=4395946
hope they reply...

guinzo said:
you can try contact santod here, but need register
http://forums.infectedrom.com/forumdisplay.php/79-Thunderbolt-Android-Development
He's last man standing Thunderbolt expert developer...
but i hear He already switch to HTC One project n leave Thunderbolt.
it very exciting news if can be true:good:
Click to expand...
Click to collapse
Santod was the reason why I loved my thunderbolt. I still have it but rarely use it. Sadly the screen is cracked but it was always a reliable phone.
Sent from my SCH-I535 using Xparent ICS Tapatalk 2

I'm sure there are more than a few people who would contribute to the cause of getting AOSP and CM11 on this phone. My old fascinate has it and so do all my other phones since.
Sent from my XT1060 using Tapatalk

TtWEAK said:
I'm sure there are more than a few people who would contribute to the cause of getting AOSP and CM11 on this phone. My old fascinate has it and so do all my other phones since.
Sent from my XT1060 using Tapatalk
Click to expand...
Click to collapse
There definitely are, but the difficulty of getting data on AOSP for this device, coupled with the age, current ownership/userbase, and developer interest translates to probably not. It's okay though, it was a great ride while it lasted.

I need help of all of you, please

I've been around in this community since 2009 if memory serves me correctly.
All this time I learned a lot from you, the community. I thank because it has served me well and thank you 1 million for the help and what they learned on the road since I joined this prestigious community.
I nedd some help.
I have long flashing, rooting, restoring and etc.
I have the full knowledge of everything about android now I want to go further and enter into the world of cooking roms
I need a mentor and people who can help me, pleasem is very apreciete

EddiePR said:
I've been around in this community since 2009 if memory serves me correctly.
All this time I learned a lot from you, the community. I thank because it has served me well and thank you 1 million for the help and what they learned on the road since I joined this prestigious community.
I nedd some help.
I have long flashing, rooting, restoring and etc.
I have the full knowledge of everything about android now I want to go further and enter into the world of cooking roms
I need a mentor and people who can help me, pleasem is very apreciete
Click to expand...
Click to collapse
You are most likely not going to find someone to show you the way. What I would recommend to you is get a nexus device or a phone that has good, solid aosp, cyanogenmod or whatever builds you are interested in and start building. When you are compiling builds from source it can be as simple as copy and paste commands into terminal or you can actually learn what each command is doing, such as make or make clean/clobber, it's up to you. You can also cherry pick certain features you may want or exclude those you don't etc.
I would not recommend the note 5 as a phone to try and learn on as you are pretty limited in what you can do currently, unlike a nexus device or something else that's supported you are not compiling with Samsung builds but rather taking a clean base and adding or removing, porting features etc. It's either a stock build, a build that has everything plus the kitchen sink tossed in or a build that's been cleaned out of stock or bloat apps/services. That's about all you can currently do with the note 5.

Learning ROM Development - Where to even begin??

So I’ve been a member here since the Droid X days and I’ve learned a lot over the years with each device I’ve had but I never really looked into creating ROMs (I always wanted to learn but never got to it).
I know it’s going to be a learning process that takes some time but I’m looking for help on where I should start. Before anyone posts a whole bunch of random looks I’ll say right now that I am a complete beginner when it comes to this stuff. I’ve looked at a bunch on threads and it’s so overwhelming being completely new so I don’t know what’s relevant and what’s not.
From the research I’ve done today I learned about a program called Android Kitchen which from my understanding was used to create and compile ROMs. From what I found it looks like the original dev stopped updating it back in 2013. In the ChefCentral>Android forum it looks like someone else took over and maintains it for Linux. I also came across a variant there called “Assayyed_Kitchen”. Is this the same program just made by someone else? I don’t know you tell me? lol
I also plan to learn some Java in the coming months and Android App development. I don’t have a huge interest in making apps right now but who knows maybe I will down the road. I just figured learning Java can only help with learning to make ROMs? Do I even need to know any of it for this kind of stuff?
So basically I’m looking for some guidance on where to start as a complete beginner in learning ROM development. Even someone taking the time to type out a few basic steps explains what the whole process even involves from start to finish would help a lot. For example..
1. Download source
2. Open in this program and blah blah
3. Do your magic and customize this and that
4. Do some more magic and pack it back up and flash
Just understanding the steps would make a huge difference because then I know what to research and what to learn. Hoping this thread gets some good info in it and maybe at some point I can create a complete noob friendly guide in the OP to help others like me who don’t know where to begin. To anyone that takes the time to reply and help out.. THANK YOU!

You download the source, edit the code you want to edit, then you compile it.
If you have more questions then that it is because you don't know enough to be able to make a ROM. Where to start? Learn how to code and compile, start compiling other peoples Roms and look at their commits and source code to see what changes they made.
You can't really drag and drop then place your logo on it.
Sent from my Pixel using Tapatalk

scryan said:
You download the source, edit the code you want to edit, then you compile it.
If you have more questions then that it is because you don't know enough to be able to make a ROM. Where to start? Learn how to code and compile, start compiling other peoples Roms and look at their commits and source code to see what changes they made.
You can't really drag and drop then place your logo on it.
Click to expand...
Click to collapse
Not sure what the attitude is for I never implied that I could do simple things like drag and drop and use others people's stuff and do it with no programming experience.
Again it's all new to me so I was asking where to start with it all. I am starting to learn Java this week and I'm trying to figure out how it all works.. I'm not interested in making android apps so the android development tutorials all over the internet wouldn't help. Yes they would help with the Java stuff but not with the ROM stuff so that's what I was trying to understand. Imagine being a complete beginner with this stuff. All this talk of compiling and GitHub and commits is all jibberish at first. You gotta start somewhere so I'm trying to get a grasp on everything. My goal is to understand the steps needed to make my own ROM first. Because once I know Step 1: use this program to do this Step 2: do this, etc.. then I know the basic overview and can start the process of actually learning the details involved in doing step 1, 2, etc

If I was teaching someone how to change a tire on a car. They first would have to understand that it involves jacking the car up, loosening lug nuts, take tires off, put new tire on, tighten lug nuts, lower car off jack. Once they get the concept and process of what they are trying to do.. then they can start learning how to jack the car up. Then how to take the lug nuts off.. and so on
If they didn't first understand the general process they might start to learn how to take the lug nuts off first and do that right away

The best place to start is to google , "how to build Android from source." This will help set up your build environment and teach you the basics. The rest is pretty much trial and error.
I started back in 2013 with one of the guides and just started messing with code. I went from not knowing any coding to compiling my first ROM(slimroms) within 2 weeks of starting. I became an official member about 2 months after starting. Here is a link to one of the guides I used to start.
http://forum.xda-developers.com/showthread.php?t=2223690

arcardinal said:
The best place to start is to google , "how to build Android from source." This will help set up your build environment and teach you the basics. The rest is pretty much trial and error.
I started back in 2013 with one of the guides and just started messing with code. I went from not knowing any coding to compiling my first ROM(slimroms) within 2 weeks of starting. I became an official member about 2 months after starting. Here is a link to one of the guides I used to start.
http://forum.xda-developers.com/showthread.php?t=2223690
Click to expand...
Click to collapse
Thanks for the link! I've done some searching around also. So I would need Linux correct? Not an issue I can partition one of my PCs just want to make sure it's definitely needed.
I think my s5 is still running slim ROM haha so thank you! Did you have any programming (Java) experience when you started?

aholeinthewor1d said:
Thanks for the link! I've done some searching around also. So I would need Linux correct? Not an issue I can partition one of my PCs just want to make sure it's definitely needed.
I think my s5 is still running slim ROM haha so thank you! Did you have any programming (Java) experience when you started?
Click to expand...
Click to collapse
I had no coding experience at all before starting.
You need Linux. You will also want a decently speced computer. I have an 8-core processor and 24 gbs of RAM and it takes about 20-30 minutes to compile a build. The computer I started on took about 4 hours.

arcardinal said:
I had no coding experience at all before starting.
You need Linux. You will also want a decently speced computer. I have an 8-core processor and 24 gbs of RAM and it takes about 20-30 minutes to compile a build. The computer I started on took about 4 hours.
Click to expand...
Click to collapse
Yikes. I have a PC I built a few years back running Windows 7 currently
-Asus P8Z77 Pro motherboard
-Intel core i5 3570k
-8GB RAM
I know I could use some more RAM but I was considering getting an SSD first. I have an ancient HDD in there now. Not sure on the exact speed but it's slow

If I was you I'd start with kernel compiling before you get into rom developing. That's what I'm doing anyway, seems like getting a rom to compile is more involving.
You would need to read up on 'git' (it's a version control program) learn some C language and also read up on another program called 'make' what it does and how it does it.
Learn about 'toolchains' how they do and which one to use. I think you can get latest toolchains by downloading android-ndk (it should be one of the folders in the zip file).
With that said you need Linux and depending on the distro you use (Ubuntu,Fedora etc) you would need to download extra packages for development and that you would have to google it to find out which ones. Also you would need to know how to navigate within Linux, use that distro's programs or tools (although 95% are the same across all distros) and all of it using only the terminal.
Google is your friend. I know it is mine. Good luck.