well i thought i'd get this up before source for JB (4.1) drops... I'm looking for a dev willing to let me watch them as they build a ROM and make changes to that ROM... no i don't need to come over your house to do this... I was thinking of a live video stream of your screen as you do the work... if you're willing to allow me to watch and maybe answer a few questions in between, i'm willing to learn!!
i learn really fast if i'm watching someone do it which is why i'm taking this approach rather than trying to read through a bunch of threads on this topic... that stuff basically looks like a foreign language to me... especially when they talk linux stuff lol... i can catch on quickly but i need to SEE IT BEING DONE... not reading and having my brain decode what i just read...
so please pass this thread along... the site i'm looking to use is join.me and it can be viewed by more than one person... so if someone else is willing to jump in on the fun and the dev is cool with it... we all can watch as they work their magic...
preferably someone that's gonna be building on crespo/crespo4g... but i'll take whoever is willing to teach!!
disclaimer: i'm not even looking for a real "expert" on the subject... just someone to do the basic work so i can take notes and then do the stuff myself!!
PM me if you're a dev and willing to help out!! what do you have to lose? nothing really... you're just gonna load the program and let it stream as you do the stuff you normall would do...
sn: it doesn't have to be Jelly Bean... but seeing as source is coming out soon... i figured someone will want to start fresh and build from aosp... that's really where i'd like to start from!!
I'd love to watch too
Sent from my SPH-D710 using Tapatalk
Click here for custom mods for your E4GT
umm. the best way to do it is to just follow the step by step guides online. doesnt get much easier than that. you watching isn't going to help when they already have all the software installed
derekwilkinson said:
umm. the best way to do it is to just follow the step by step guides online. doesnt get much easier than that. you watching isn't going to help when they already have all the software installed
Click to expand...
Click to collapse
thanks but i have everything i need to build a ROM installed and have already built one from CM9 source... i'm talking about all the other edits and things they do... ie: adding in or removing features of a ROM...
and if you re-read my OP... i said reading this stuff is like learning another language... i'm a visual learner... i need to SEE these things then do them... not read them and try to decode whatever i just read...
the1dynasty said:
thanks but i have everything i need to build a ROM installed and have already built one from CM9 source... i'm talking about all the other edits and things they do... ie: adding in or removing features of a ROM...
and if you re-read my OP... i said reading this stuff is like learning another language... i'm a visual learner... i need to SEE these things then do them... not read them and try to decode whatever i just read...
Click to expand...
Click to collapse
I just happen to work for a company the makes tools to help visual learners.
Sent from my SPH-L710 using Tapatalk 2
Yea I'm willing too. I got a few things going here. Along with ubuntu, sdk, java6, android kitchen. I'm more of a visual learner. I've been constantly researching to point where my brain hurts to think android. I need a break. But I'm willing as well. Some devs out there no even respond to help needed. I would love to watch Fergie716 at work tho.
Sent from my Nexus S 4G using Tapatalk 2
My video will be up tomorrow (today) in my MIUI thread. I have everything ready for it. I just had a bit too much to drink tonight (its 450am)
Tomorrow afternoon it'll be up
Sent from my SPH-L710 using Tapatalk 2
I also like to watch.
Sent from my SPH-D710
I agree with the OP, one thing I think is missing (or at least in my experience hard to find) in the Android ROM community is a set of guides on how to properly do things (branch with repo to make a mod, apply patches from other trees, add prebuilt apks, add source provided apps, integrate su, busybox, creating your own vendor, device, adding your kernel, etc)
It's all scattered all over the net, sure you can figure some of it out but if you lower the barrier of entry people will be able to focus their energy on doing better work somewhere else.
gparent said:
I agree with the OP, one thing I think is missing (or at least in my experience hard to find) in the Android ROM community is a set of guides on how to properly do things (branch with repo to make a mod, apply patches from other trees, add prebuilt apks, add source provided apps, integrate su, busybox, creating your own vendor, device, adding your kernel, etc)
It's all scattered all over the net, sure you can figure some of it out but if you lower the barrier of entry people will be able to focus their energy on doing better work somewhere else.
Click to expand...
Click to collapse
i really couldn't have said it any better!!
i know Fergie usually puts out some great tutorials... i used his stuff when i was learning to theme... so hopefully he delivers on this as well... i would still like to do a live "webinar-type" of training tho if any dev is up for that!!
we can get a time going so that everyone can login at the same time and see what's being done...
I'd also like to see how its done, I would love to be able to cook up some things and then release a ROM to the public. I'm sure it's not easy but I'm willing to take a wack at it
Btw are you guys using pretty powerful computers for building ROMS? Or would you say they're average spec?
stellar said:
I'd also like to see how its done, I would love to be able to cook up some things and then release a ROM to the public. I'm sure it's not easy but I'm willing to take a wack at it
Btw are you guys using pretty powerful computers for building ROMS? Or would you say they're average spec?
Click to expand...
Click to collapse
mine isn't that great tbh... but it manages to put out something... once your setup is correct and you do your first build... the second build of that ROM is usually a lot faster...
i think average would be around quad core with 8GB RAM... that's my guess based on a few devs i've heard from...
the1dynasty said:
mine isn't that great tbh... but it manages to put out something... once your setup is correct and you do your first build... the second build of that ROM is usually a lot faster...
i think average would be around quad core with 8GB RAM... that's my guess based on a few devs i've heard from...
Click to expand...
Click to collapse
I like to learn too. But my pc is just dual core 3.0ghz 4gig ram what do you think?
Sent from my Nexus S™
mixtapes08 said:
I like to learn too. But my pc is just dual core 3.0ghz 4gig ram what do you think?
Sent from my Nexus S™
Click to expand...
Click to collapse
it will take longer than some other PC's... but that will still work... i'd guess a few hrs to build a ROM... mine is around those specs and it takes a few hrs on the initial build lol
There should also be a thread for porting, kinda like "chef central" where users could get support on certain issues with their ports.. Over there in chef central the people seem to only help people that are building from source.. there's not too much support for people doing ports which is unfortunate because not everyone is skilled enough to build from source and having ports is what keeps some devices alive... In this thread there would be threads where you could post your logcat if your not getting boot and some of the more experienced porters (like fergie for example) could take a look and point you in the right direction. Also there could be guides and tutorials as how to get certain aspects of the ROM working like HWA, WiMax, MMS/SMS so on and so forth... I think that it would really bring a lot of new life to some devices that don't get the support that they should..
Anyone else agree on that or is just me?
evol4g said:
there's not too much support for people doing ports which is unfortunate because not everyone is skilled enough to build from source and having ports is what keeps some devices alive...
Anyone else agree on that or is just me?
Click to expand...
Click to collapse
I agree with the whole sentiment "more people should build things", but not with "aosp is too hard so we should help people do ports". Unless a port is the only way to get a device working, we definitely should focus on making aosp easier to learn if that's part of a problem the porting people are having.
Anyway, I started my own ROM yesterday and might end up making a wiki to document a bunch of things I'm doing. It's a very stock-ish ROM though, so I won't spend much time writing about adding mods other than a few basic ones.
-IF- I do get around to making the wiki, I will post here about it.
As for the computer, I am using a i7 930 (2.8GHz) with 24GB of RAM.
gparent said:
I agree with the whole sentiment "more people should build things", but not with "aosp is too hard so we should help people do ports". Unless a port is the only way to get a device working, we definitely should focus on making aosp easier to learn if that's part of a problem the porting people are having.
Anyway, I started my own ROM yesterday and might end up making a wiki to document a bunch of things I'm doing. It's a very stock-ish ROM though, so I won't spend much time writing about adding mods other than a few basic ones.
-IF- I do get around to making the wiki, I will post here about it.
As for the computer, I am using a i7 930 (2.8GHz) with 24GB of RAM.
Click to expand...
Click to collapse
id like to ask.. is making a rom really difficult.. how much java language knowledge would a person need to have to build from source...?
ferozfero said:
id like to ask.. is making a rom really difficult.. how much java language knowledge would a person need to have to build from source...?
Click to expand...
Click to collapse
Well, one of the fun things about being a maintainer rather than a developer is that you really don't -need- much knowledge at all.
Everything helps, though. Yesterday I fixed a gcc compilation issue from knowledge of C++ that I acquired over a number of years. It wasn't a hard bug to fix and I could've asked a friend about it instead, but being a programmer lets me get away with fixing mistakes I see in AOSP when it's necessary (it rarely is).
Later, in my kernel compile, I turned on a compilation flag because I knew that a warning (that failed the build due to -Werror) was completely inaccurate. Good luck doing this if you don't know what's a compilation flag, and good luck doing it safely if you're not sure what the warning means and if it is really safe to override it (it often isn't).
If you want to make a ROM and be efficient about it, I think the two most important skills (in order of importance) are the ability to use git and to solve problems. Without a minimum of source control ease, it will be a pain in the ass to add features to your mods or to keep track of changes efficiently (especially when it comes the time to branch off releases and what not). Problem solving is what you do whenever stuff that should work doesn't work. And it's always hard because if it wasn't hard it would be documented already so you wouldn't have the problem.
If you want to build FEATURES for a mod (that is, not repack what others have written), then yes you will need programming knowledge. Java, C and probably C++. Mostly Java for user facing stuff.
great post gparent... that was a wonderful breakdown of how ROM making works... if it's all true (which it sounds like it), then this might be a bit more than i can chew lol... i'm still willing to see someone in action do these things so i have a better understanding of how to put things together and maybe one day i'll take a stab at building my own ROM!!
gparent said:
24GB of RAM.
Click to expand...
Click to collapse
:what: wow, lol
If any other devs come by I'd love to know what setups you guys use for developing too.
Sent from my SPH-D710 using Tapatalk
Click here for custom mods for your E4GT
Related
I always wanted to share this as some people call themselves developers in this forum by just removing and adding some apps and making roms "look faster". What they is actually going into the app called spare parts and choose the fast transition and fast windows animations. So why not trying these settings on cm7 and see which is faster people? Or any other rom developed by true developers!! I am not saying im against rom development but at least if u are trying to develop then do something unique and not a rom that even my grandma could do
Sent from my HTC Vision using XDA Premium App (cm7)
I agree mostly... the vast majority of roms available for us right now are just themed CM7. that's fine and dandy, but it's particularly amusing to me when people talk smack about CM7 being "slow" or "buggy" etc and then claim their new rom of choice, a CM7 variant, is the best thing since sliced bread.
that said, even theming can be a hell of a task, and extremely time consuming. I appreciate all of the work the development community provides to us (free of charge, mind you).
I don't see what you are trying to get at here. For a start I have tried just about every rom there is and I don't believe I have ever come across one that has window tansitions set to fast by default. We have a really good mix of devs here doing different things and do great work. You need to remember that devs build a rom that they like, quite often it is built for them and they choose to release it to the general public.
One of the great things about this community is choice. A rom that one person loves and another will hate, its all about personal preference.
Do you know anything about developing a rom? I don't but I knw a lot of work goes in to them and the devs do a lot more than change some settings on spare parts to make there rom different, better and faster than the next rom.
Your post in insulting to the devs that work really hard to give us something cool and awesome.
Sent from an ice cream sandwich
Well said. You must strive to support to the best of your abilities, the development scene for this respective phone.
Sent from my GT-I9000 using XDA App
There is a MAJOR difference between Chef and Developers, that's why we have the term Chef for non devs that make ROMs.
I never said not supporting TRUE dev!! Im referring to those that call themselves devs by removing and adding a few apps. Go into other handsets forums and see what i mean. For ouf g2 only a few deserve to be called devs. Thats what im saying..
Sent from my HTC Vision using XDA Premium App
I know who your referring to, and if your not referring to someone in particular, there is someone who repackages stuff that offers nothing new and everyone wets there pants over it. Getting on my nerves somewhat.
Sent from my HTC Vision using XDA Premium App
TheDeadCpu said:
There is a MAJOR difference between Chef and Developers, that's why we have the term Chef for non devs that make ROMs.
Click to expand...
Click to collapse
And does anyone actually use the chef title here on the g2 forum? No....
Sent from my HTC Vision using XDA Premium App
I think this thread really exemplifies a major issue in the dev community: The lack of drive for a unified stable product whose basic functions all work properly across a cross section of devices.
Theaming is all well and good, but if MMS doesn't work and you have force crashes on multiple internal apps; what exactly is it all good for? If I can't boot up gps, then what the heck does it matter? If internal components and tweaks are confusing and ill thought out, then why the heck are they being shared?
I really think that the dev community needs to sit down across multiple devices & hash these issues out.
astriaos said:
I think this thread really exemplifies a major issue in the dev community: The lack of drive for a unified stable product whose basic functions all work properly across a cross section of devices.
Theaming is all well and good, but if MMS doesn't work and you have force crashes on multiple internal apps; what exactly is it all good for? If I can't boot up gps, then what the heck does it matter? If internal components and tweaks are confusing and ill thought out, then why the heck are they being shared?
I really think that the dev community needs to sit down across multiple devices & hash these issues out.
Click to expand...
Click to collapse
Yohu know what your looking for? A stock rom....they all work! The devs here are pushing the boundries and taking our phones to the edge! Of course not everything will work out of the box and if they fixed everything before they released it they would have to deal with everyone begging for the next release.
Sent from my HTC Vision using XDA Premium App
xsteven77x said:
I know who your referring to, and if your not referring to someone in particular, there is someone who repackages stuff that offers nothing new and everyone wets there pants over it. Getting on my nerves somewhat.
Sent from my HTC Vision using XDA Premium App
Click to expand...
Click to collapse
Thats what im talking about. I m glad someone agrees with me.. cheers mate
Sent from my HTC Vision using XDA Premium App
kokoskokis544 said:
Thats what im talking about. I m glad someone agrees with me.. cheers mate
Sent from my HTC Vision using XDA Premium App
Click to expand...
Click to collapse
Thought I was the only one too but did not want to be rude or sound ungrateful. I do appreciate every quote on quote devs work and passion for making us roms. But some of these are just stock with the equivelant of removing bloat with titanium backup. No system tweaks. Nothing really even changed. if anything they should just be called bloatless roms or something.
On another note, while I do get annoyed that a lot of stuff is just cyanogen with a slick of paint on it, obviously the work it takes to build a rom from the ground up is not easy. Otherwise we would see a lot more of them. I do understand that and do not take lightly how hard it probably is. Maybe the answer is let's port some roms from other phones? Like insertcoin for example? Or maybe all the devs that are just repackaging stuff get together and form something along the lines of what the bionix team does and all work together to make one super good rom.
I LOVE the choices we have with this phone. Its f-in awesome. But sometimes I feel like its just a placebo with really one 3 to 4 actual unique roms for our g2. I do not know how to make roms, so I'm not acting like this can be done overnight. But some of this just seems like common sense no matter what angle your coming from.
Obviously rmk is a rom god. And suilmagic seems like an up and comer. Pershoots kick ass. I thought for a minute there was many a rumor that eugene was heading our way, which if true would probably cause a dam near astronomical shift in this forum, hope there is some truth to that rumor. Those are devs that stand out to me, if I didn't say your name I just didn't think of you when I was writing this.
Thank you for indulging my two cents. I do not mean to offend anyone whatsoever. I appreciate everything you guys do for us. But let's not sugarcoat the reality of our situation.
Sent from my HTC Vision using XDA Premium App
kokoskokis544, welcome to the club
what enrages me the most is the absence of detailed information on what exactly is done to the rom - goes against the community spirit.
I would like to research the changes myself and make sure there's nothing that can damage my phone.
actually, from my point of view, the worst thing is when someone does not give deserved credit - "Grab, use and forget"
petarpLab said:
kokoskokis544, welcome to the club
what enrages me the most is the absence of detailed information on what exactly is done to the rom - goes against the community spirit.
I would like to research the changes myself and make sure there's nothing that can damage my phone.
Click to expand...
Click to collapse
I agree that is extremely annoying. And then you ask what is it in it or whats different from other roms and you get a "INSTALL IT STUPID AND FIND OUT"....YA WELL UP YOURS TOO
even decompiling a rom and making minor changes like adding/removing apks and tweaking existing settings takes hours of work. theming is even more time consuming. I don't think most people realize this. the work itself isn't "hard," but the amount of time you have to set aside to be able to do this kind of stuff is extremely tough to come by, at least for me.
in that respect, you should all be grateful for the time ALL devs and chefs, regardless of the substance of their contributions, devote to giving us new stuff to play with.
pmcqueen said:
even decompiling a rom and making minor changes like adding/removing apks and tweaking existing settings takes hours of work. theming is even more time consuming. I don't think most people realize this. the work itself isn't "hard," but the amount of time you have to set aside to be able to do this kind of stuff is extremely tough to come by, at least for me.
in that respect, you should all be grateful for the time ALL devs and chefs, regardless of the substance of their contributions, devote to giving us new stuff to play with.
Click to expand...
Click to collapse
I'm glad there is at least one person here that share my point of view.
[sig]My mission is to hit 1000 posts by 23/05/2011[sig]
cjward23 said:
I'm glad there is at least one person here that share my point of view.
[sig]My mission is to hit 1000 posts by 23/05/2011[sig]
Click to expand...
Click to collapse
Make that two. I don't really see a reason to get all aggro over something that is free. As to something that "might damage my phone".... um.. what? To my knowledge, the devs (or whatever some may wish to call them) are not into the practice of putting out toxic software for us to download. To make sure, I use this goofy thing called judgement. I'll look at a new ROM, read the dev comments, wait a while, read the feedback comments, and make a decision. Not complicated. If there are a ton of bugs and problems, I'll wait until later versions come out that correct these issues. Or I'll choose another ROM. I honestly don't see the point of complaining about free services and a plethora of options. If people don't like all that, unroot and stay with stock software.
cjward23 said:
I'm glad there is at least one person here that share my point of view.
Click to expand...
Click to collapse
No, I'm with you too. While I don't know zip about development, I can appreciate the fact that it takes time and effort to create and upload a ROM, even one that is just a tweaked version of someone else's work.
While the OP seems to be complaining about one or a few people in particular, it seems that many people who post ROMs are doing it for the sheer enjoyment, or to create something unique for themselves. Then, they go out of their way to upload and post it on here for others to enjoy. Of course, giving credit when its due, and describing what has been changed (and what hasn't), as previously suggested, are all good points as well.
Its not like there is a whole lot of fortune and glory associated with calling yourself a "developer". If somebody is even calling themselves that, its probably due to lack of a better term, more than anything else. Its a bit cumbersome to go around calling yourself "Guy who modified a ROM for myself, and now posting it for others to enjoy".
Besides, if you don't like a person's ROMs, just don't use them or read his threads. Not enough ROMs tends to be the more common complaint, rather than too many (although obviously quality is a factor as well, not just quantity).
If you really wanna ***** about free services then don't use them, switch phones, go to a different dev community. People do this work for fun, they don't ask for money for the hours of work they put in. You should be appreciative for whatever ROMs we get ,especially if you don't "dev" yourself.
Sent from my HTC Vision using XDA Premium App
With the newly deodexed honeycomb I have gotten the itch to start looking into how to create/develop my own rom.
What is the best way to start learning, is there a good starting point, I have been doing some reading but it just seems so overwhelming.
I do have basic Linux knowledge and can whip up a linux VM in no time to get crackin. I have been modding my EVO for the last year so i know how to be a "user" and have tinkered with the xoom but have only scratched the surface.
So my question is just this, Where to start??
any input would be helpful.
+1!
need a little walkthrough too :S!!
and someone can say what files NEVER EDIT to not brick the xoom!!
i too would be highly interested in learning what steps to take.
bossjeeves said:
With the newly deodexed honeycomb I have gotten the itch to start looking into how to create/develop my own rom.
What is the best way to start learning, is there a good starting point, I have been doing some reading but it just seems so overwhelming.
I do have basic Linux knowledge and can whip up a linux VM in no time to get crackin. I have been modding my EVO for the last year so i know how to be a "user" and have tinkered with the xoom but have only scratched the surface.
So my question is just this, Where to start??
any input would be helpful.
Click to expand...
Click to collapse
Get that VM set up, and get your environment set up so you can build AOSP.
Look through the source so you know what parts of Android are found where in the tree.
Learn a little about the platform, what does what...
Basically, just get your hands dirty.
ydaraishy said:
Get that VM set up, and get your environment set up so you can build AOSP.
Look through the source so you know what parts of Android are found where in the tree.
Learn a little about the platform, what does what...
Basically, just get your hands dirty.
Click to expand...
Click to collapse
so this is kind of what I expected for an answer but I would like a little more if you dont mind.
Like maybe a couple of links pointing in the right direction, like what does the environment need for tools etc.
ydaraishy said:
Get that VM set up, and get your environment set up so you can build AOSP.
Look through the source so you know what parts of Android are found where in the tree.
Learn a little about the platform, what does what...
Basically, just get your hands dirty.
Click to expand...
Click to collapse
That's like saying jump in a lions den and see what ticks him off. Can we get more details please? I want to get into theming and want to know the ideal OS to do it on. I was hoping on doing it in Linux but want advice from themers.
IV been playing hippie for a couple of weeks so I don't know if I missed something but, unless the full AOSP source has been released, a deodex rom will help with nothing but theming.
You can't do much to customise a ready built rom, and you would be wasting your time to try anything but the simplest of mods.
That being said, if you're happy to play with smali you might achieve a little more.
Sent from my HTC Desire using Tapatalk
alias_neo said:
IV been playing hippie for a couple of weeks so I don't know if I missed something but, unless the full AOSP source has been released, a deodex rom will help with nothing but theming.
You can't do much to customise a ready built rom, and you would be wasting your time to try anything but the simplest of mods.
That being said, if you're happy to play with smali you might achieve a little more.
Sent from my HTC Desire using Tapatalk
Click to expand...
Click to collapse
this is exactly what I am talking about here, This is kind of why I brought it up in the xoom forum, since we dont have source and we do have a deodexed rom wouldnt playing with that be a great place to start? if so like what would be the best place to start, you say play with smali, now I know I can google and get tons of answers but I am asking to explain a little more because I trust the feedback from here and I think others might benefit also
bossjeeves said:
this is exactly what I am talking about here, This is kind of why I brought it up in the xoom forum, since we dont have source and we do have a deodexed rom wouldnt playing with that be a great place to start? if so like what would be the best place to start, you say play with smali, now I know I can google and get tons of answers but I am asking to explain a little more because I trust the feedback from here and I think others might benefit also
Click to expand...
Click to collapse
Smali is a tool that will reverse engineer (baksmali) dalvik byte code into (barely) human readable code. If you can learn to understand this you can reverse and modify stuff with it. If i remember right, brut.all is the guy responsible, have a read around, but i warn you, its not for the feint of heart.
Macbots drool as I XOOM through the Galaxy to my hearts Desire.
bossjeeves said:
this is exactly what I am talking about here, This is kind of why I brought it up in the xoom forum, since we dont have source and we do have a deodexed rom wouldnt playing with that be a great place to start? if so like what would be the best place to start, you say play with smali, now I know I can google and get tons of answers but I am asking to explain a little more because I trust the feedback from here and I think others might benefit also
Click to expand...
Click to collapse
Here is one of the best sources I've found....... made by cyanogen himself, tonnes of info here.
http://forum.xda-developers.com/showthread.php?t=667298
I did come across this link http://simply-android.wikia.com/wiki/ROM_Development
looks like something that would be a helpful start. thoughts?
ps thanks for the replys
I think the best way to learn anything is just to read a lot, and to search for any questions you have. There are a thousand ways to learn to hack, but they all require the initiative to find answers on your own.
Sorry if this sounds patronizing. I always hated it when I get on a board and ask for something, and some curmudgeon geek tells me "Google is your friend". But it's true. You get better answers faster, as you can avail from the entire Internet, as opposed to the small number of people who reply to your query.
Thanks to the dude who linked to the Cyan advice post. My takeaway is this one line:
"There is a *ton* of information out there but any kind of "step-by-step rom cooking guide" is going to be a complete fail- it's too broad of a subject."
IMO if you are serious about ROM hacking, you need a dedicated linux environment. Cygwin is OK for run-time stuff, but too limited for anything else. If you only want to run basic bash commands, a simpler solution is win-bash (http://win-bash.sourceforge.net).
I'm kinda in the same shoes you are. Android interests me, although I don't have a Xoom or an Android tablet for that matter. Was gonna get a HC tab to tinker, but HC is still too green, so decided on a Nook Color for educational purposes. It's been out a while, and has many hacks already done that I can peruse. That, and it'll be useful for my "read a lot" mantra above.
So we have it for the fascinate, the vibrant, the Nexus s and the galaxy s its self, where is ours? If we had Cyanogenmod all of this garbage about waiting for sprinsung to update our GB would be a non-issue. i have programming skills (java, python, c++, perl, bash, etc) and a lot of free time. Id be willing to put forth effort to get this out if some one were to decide to help out.
If OP really does have the knowledge to help out hes more than welcome to take a stab at it.. but be warned people have tried and tried but dont realise the level of development they are up against. the team working on it are very good, and if you think you have something to add.. then come to the cm7 epic irc channel and chit chat, but i wouldnt expect them to automatically assume you know what youre talking about...
Without GB source code, this is a dead end
Sent from my MIUI Powered device
krazyflipj said:
Without GB source code, this is a dead end
Sent from my MIUI Powered device
Click to expand...
Click to collapse
Not at all. Without Gingerbread Source Code Developers are capable of writing drivers themselves, it is just a lot easier to work with Samsung's drivers.
063_XOBX said:
Not at all. Without Gingerbread Source Code Developers are capable of writing drivers themselves, it is just a lot easier to work with Samsung's drivers.
Click to expand...
Click to collapse
Exactly...as everyone always asks "why do the other Galaxy S line of phones have CM7 but not us?" Well, since those models will probably never see official GB, the Devs in those communities took it upon themselves to build CM7 from scratch, from the bottom up. Just to point it out as well, they're Dev's are a lot higher in numbers compared to ours and therefore were able to split the work amongst themselves, which was still a challenge to say the least. We on the other hand, have a lot less Devs and us trying to follow the other Galaxy S communitie's footsteps would be impossible. The workload is just too much for our Devs. Luckily, we were the only US Galaxy S variant that will be receiving official GB, so, our Devs are waiting on Samsung to release source code, as this will make everything that much easier and smoother to complete CM7. I mean, why try and build from scratch when we have GB being released in a couple weeks? and just one last thing to clear up...everyone asks "why not just port a kernel or ROM from another Galaxy S phone?" Well, the Epic is the 'redheaded stepchild' of the Galaxy S family. Our hardware is different from the rest of the other variants. Decad3nce and the rest of the CM7 team have assured us that they've exhausted many different resources in attempts to get us CM7 before GB, but so far, they're still not near releasing a stable build.
Bottom line: GB source will help up immensely and is what we're currently waiting/looking forward to in order to advance with CM7 development.
*this is all common knowledge I have read/have been told by many high reguarded ppl within and around our community. If I'm wrong about something please point it out an correct me, just plz dnt start a flame war or anything of the like. I wrote this in hope of clearing up some questions/concerns. Also, feel free to add anything I might have missed*
Sent from my SPH-D700 using XDA App
metalblaster said:
So we have it for the fascinate, the vibrant, the Nexus s and the galaxy s its self, where is ours? If we had Cyanogenmod all of this garbage about waiting for sprinsung to update our GB would be a non-issue. i have programming skills (java, python, c++, perl, bash, etc) and a lot of free time. Id be willing to put forth effort to get this out if some one were to decide to help out.
Click to expand...
Click to collapse
i n00b teh pwns said:
Considering we have a team working on it, these threads aren't necessary. Making these threads just makes the Devs realize how ungrateful you people are. If I was them, I would've scrapped CM7 work a long time ago.
Sent from my Frozen over Epic.
Click to expand...
Click to collapse
chris41g said:
If OP really does have the knowledge to help out hes more than welcome to take a stab at it.. but be warned people have tried and tried but dont realise the level of development they are up against. the team working on it are very good, and if you think you have something to add.. then come to the cm7 epic irc channel and chit chat, but i wouldnt expect them to automatically assume you know what youre talking about...
Click to expand...
Click to collapse
All of you are right.
Coming from someone who has a lot of experience developing BSPs for the Linux kernel, this is something that can take a lot of time.
Some of it can be reverse engineered, but a lot of it only exists in binary form. Unfortunately, the interfaces to the binary parts can change.
It's not quite as simple as knowing C/C++. You have to know how the hardware works, or at least similar experience to know what's going on and how to reverse engineer it.
metalblaster said:
So we have it for the fascinate, the vibrant, the Nexus s and the galaxy s its self, where is ours? If we had Cyanogenmod all of this garbage about waiting for sprinsung to update our GB would be a non-issue. i have programming skills (java, python, c++, perl, bash, etc) and a lot of free time. Id be willing to put forth effort to get this out if some one were to decide to help out.
Click to expand...
Click to collapse
Everything should be current here: https://github.com/EpicCM
Otherwise, feel free to jump in #epic @ irc.fossnet.info
*Please no one delete this thread! It is really important!*
Hi everyone!
I am here to tell you guys about our phone.
Yes, the title says everything; our phone is not dead!
What do you think? Just because Huawei is not supporting this phone anymore doesn't mean that our phone is dead!
Look! We have achieved great things with our knowledge! We have already have Android that wasn't given to us by Huawei:
- CM 7.2
- Aurora ICS
- MIUI
- Oxygen
- JokerROM
- and lots of others!
(Thanks to all those developers that have contributed their efforts for the sake of our phone!)
Huawei is not supporting us, but every person in our community is supporting each other.
I know we are lacking developers, but we still have great developers: DZO (he's a bit sleepy), forumber2, Blefish, MosTERRA, ezet, and anyone else I have missed!
We still have developers, but not once have I read anyone commenting anything positive about our phone. Not once anyone has told someone else that our phone is dying/dead. Always, everyone here has said our phone is finished.
Come on guys! Don't say this! Always try to say good things about our phone. By saying bad things about our phone, you are discouraging other people, and most importantly the Developers, from keeping the phone.
Please stop discouraging Developers and others! Instead, encourage others to gather knowledge and start building some ROMs!
Yes, I would encourage all of you here to start gathering knowledge about android and start building some MODs, Themes, ROMs, etc, for our phone!
NEVER AGAIN I WOULD WANT TO SEE A COMMENT THAT SAYS NEGATIVE THINGS ABOUT OUR PHONE!!!!
You're right and in general I agree with you but this sub-forum is only to post ROM's preferably tested and without bugs. You should move this to General section or ask to mods to do that. Blefish is working on CM 10 and we (non-developers) need to wait.
Cheers.
to say our phone is "dead" is not negative as i perceive it.. its just a plain fact..
in this fast-changing technology world, our phone already did its job very well..
my u8800 has just passed its 2-year mark, and though its just become my second-line support phone in this month, its still of great value to me..
(big compliment to our great developers!)
HOWEVER, the phones is already over 2 years old, and this is a very old age in technology world (and also considering its lack of official support)..
if everyone just refuses to proceed forward, we are probably still playing/flashing mods for our beloved transistor radio (if thats even possible)!
[edit]
with the above said, i do not mean to discourage any further development effort on this phone..
i actually welcome such activities very much honestly..
its just that ppl should also recognise those of us who try to move forward with newer and more powerful phones..
rqmok said:
*Please no one delete this thread! It is really important!*
Hi everyone!
I am here to tell you guys about our phone.
Yes, the title says everything; our phone is not dead!
What do you think? Just because Huawei is not supporting this phone anymore doesn't mean that our phone is dead!
Look! We have achieved great things with our knowledge! We have already have Android that wasn't given to us by Huawei:
- CM 7.2
- Aurora ICS
- MIUI
- Oxygen
- JokerROM
- and lots of others!
(Thanks to all those developers that have contributed their efforts for the sake of our phone!)
Huawei is not supporting us, but every person in our community is supporting each other.
I know we are lacking developers, but we still have great developers: DZO (he's a bit sleepy), forumber2, Blefish, MosTERRA ezet, possibly me, and anyone else I have missed!
We still have developers, but not once have I read anyone commenting anything positive about our phone. Not once anyone has told someone else that our phone is dying/dead. Always, everyone here has said our phone is finished.
Come on guys! Don't say this! Always try to say good things about our phone. By saying bad things about our phone, you are discouraging other people, and most importantly the Developers, from keeping the phone.
Please stop discouraging Developers and others! Instead, encourage others to gather knowledge and start building some ROMs!
Yes, I would encourage all of you here to start gathering knowledge about android and start building some MODs, Themes, ROMs, etc, for our phone!
NEVER AGAIN I WOULD WANT TO SEE A COMMENT THAT SAYS NEGATIVE THINGS ABOUT OUR PHONE!!!!
Click to expand...
Click to collapse
So why don't you make Jelly bean ?
iamelton said:
to say our phone is "dead" is not negative as i perceive it.. its just a plain fact..
in this fast-changing technology world, our phone already did its job very well..
my u8800 has just passed its 2-year mark, and though its just become my second-line support phone in this month, its still of great value to me..
(big compliment to our great developers!)
HOWEVER, the phones is already over 2 years old, and this is a very old age in technology world (and also considering its lack of official support)..
if everyone just refuses to proceed forward, we are probably still playing/flashing mods for our beloved transistor radio (if thats even possible)
Click to expand...
Click to collapse
Our main problem is the just the lack of developers as I already said before, because saying our phones is old fashioned it ain't true, for an example the Huawei Ascend G300, imo that phone is not that far away from our phone in hardware and capability (and also it was release in May of 2012), but still it already has CM9, CM10, CM10.1, thats my point of view, we can't all have the same opinion. I just don't have the skill to do such things in the Android area, if I had I would work on this awesome device.
It's not dead, but it's been on life support for a very long time, now. Blefish is the only active, transparent developer this device has going for, and even he doesn't have public releases yet and encounters numerous issues. There is no real Jellybean for this device, regardless of the fact that the hardware is capable, and so for all intents and purposes it is dead, for the time being. But that could change.
Regardless, this is a terrible thread and if you want to help you shouldn't spam this forum. There are specific forums for this sort of inane garbage.
I think it's dead anymore since we can't go through jellybean. There are only 2 person as i know who have coding knowledge;dzo and blefish.Besides we haven't seen a working wifi for jellybean both of them;so this makes the phone dead,in my view.
i think the points are quite clear now.. in android world, a phone is "dead" if there is not much active development/support for the latest updates going around (either officially or from individuals)..
[edit]
OP, just did a search and found out that u ported a xperia style rom to our phone, so that makes u a developer of this phone.. thx for the work..
(though another GB rom does not interest me that much.. )
I'd like to point out that just because I haven't released a rom does not mean I am not working on it. Just hang on as there is awesome stuff coming up!
I know I am not the fastest developer around, but I always try to do things "properly". Of which I mean I try to provide good code that would be reusable in the future.
Sent from my U8800
Would just like to clarify something
No. Our phone will never be dead, as long as we have devs working on it.
I would also like to point out something:
Just because I ported Xperia Style GB ROM, doesn't mean I have become a developer. BUT at least I am trying to build JB for our device. Yes, I have downloaded the CM10 source and have started building it. Since this is the first ever ROM I will build, which is why I am getting help from Blefish (thanks a lot Blefish. I really appreciate your efforts).
I am trying my best to keep this project going, but I have my studies and other important things (won't mention because they are personal). It is my second last year in High School, so I don't get much time (i'm sorry).
I WOULD STILL LIKE TO ENCOURAGE PEOPLE TO GATHER KNOWLEDGE AND START BUILDING FOR OUR DEVICE. WE NEED AS MUCH DEVELOPERS AS POSSIBLE WORKING ON THIS DEVICE!
I know gathering the knowledge is hard, but we have the Q&A section where you can ask something whenever you are stuck. Please step forward and start working!
Thanks for understanding.:good:
rqmok said:
No. Our phone will never be dead, as long as we have devs working on it.
I would also like to point out something:
Just because I ported Xperia Style GB ROM, doesn't mean I have become a developer. BUT at least I am trying to build JB for our device. Yes, I have downloaded the CM10 source and have started building it. Since this is the first ever ROM I will build, which is why I am getting help from Blefish (thanks a lot Blefish. I really appreciate your efforts).
I am trying my best to keep this project going, but I have my studies and other important things (won't mention because they are personal). It is my second last year in High School, so I don't get much time (i'm sorry).
I WOULD STILL LIKE TO ENCOURAGE PEOPLE TO GATHER KNOWLEDGE AND START BUILDING FOR OUR DEVICE. WE NEED AS MUCH DEVELOPERS AS POSSIBLE WORKING ON THIS DEVICE!
I know gathering the knowledge is hard, but we have the Q&A section where you can ask something whenever you are stuck. Please step forward and start working!
Thanks for understanding.:good:
Click to expand...
Click to collapse
HD2 is dead and it still has developers.
It's not developing, it's passed on. This phone is no more. It has ceased to be. It's expired and gone to meet its maker. This is a late phone. It's a stiff. Bereft of life, it rests in peace. If we haven't bought it , it would be pushing up the daisies. It's run down the curtain and joined the choir invisible. This is an ex-phone. Capisci?
rqmok said:
No. Our phone will never be dead, as long as we have devs working on it.
I would also like to point out something:
Just because I ported Xperia Style GB ROM, doesn't mean I have become a developer. BUT at least I am trying to build JB for our device. Yes, I have downloaded the CM10 source and have started building it. Since this is the first ever ROM I will build, which is why I am getting help from Blefish (thanks a lot Blefish. I really appreciate your efforts).
I am trying my best to keep this project going, but I have my studies and other important things (won't mention because they are personal). It is my second last year in High School, so I don't get much time (i'm sorry).
I WOULD STILL LIKE TO ENCOURAGE PEOPLE TO GATHER KNOWLEDGE AND START BUILDING FOR OUR DEVICE. WE NEED AS MUCH DEVELOPERS AS POSSIBLE WORKING ON THIS DEVICE!
I know gathering the knowledge is hard, but we have the Q&A section where you can ask something whenever you are stuck. Please step forward and start working!
Thanks for understanding.:good:
Click to expand...
Click to collapse
ok i take back my previous recognition of u as a developer.. now you are a developer-to-be for this great phone.. (honestly, no sarcasm attached.. )
and while i think u8800 is dead, u see it as a living pal.. no problem.. case closed.. (no sarcasm, again..)
now back to business.. i would very much be happy to see a jb rom created and surely would give it a try in my u8800..
i just hope u can keep this enthusiasm and keep working on this jb-rom-to-come..
honestly speaking, having enthusiasm on something and start working on it are not that difficult.. its the persistence and patience (in dealing with obstacles) that make the difference..
good luck and hope to hear from u soon.. :good:
Blefish said:
I'd like to point out that just because I haven't released a rom does not mean I am not working on it. Just hang on as there is awesome stuff coming up!
I know I am not the fastest developer around, but I always try to do things "properly". Of which I mean I try to provide good code that would be reusable in the future.
Sent from my U8800
Click to expand...
Click to collapse
Hey,
I just don't understand something so i want to ask you. I am following you on twitter and see that it is really not easy making kernel 3.4. I just want to know, wouldn't it be easier if you just use the 3.0.8 kernel that we already have and maybe tweak it a bit? 3.0.8 should work with CM10. I just don't see the point of triing so hard to make the new kernel for CM10. Let's look in the future and if you release your rom in 2 months for now there will not be so many people that would find it usefull because many of U8800 users are already switching to new devices. And in may there is coming KLP.
Thanks for clarification! :good:
rastek said:
Hey,
I just don't understand something so i want to ask you. I am following you on twitter and see that it is really not easy making kernel 3.4. I just want to know, wouldn't it be easier if you just use the 3.0.8 kernel that we already have and maybe tweak it a bit? 3.0.8 should work with CM10. I just don't see the point of triing so hard to make the new kernel for CM10. Let's look in the future and if you release your rom in 2 months for now there will not be so many people that would find it usefull because many of U8800 users are already switching to new devices. And in may there is coming KLP.
Thanks for clarification! :good:
Click to expand...
Click to collapse
I understand what you are trying to say to Blefish.
I'll tell you. May it be 3.0.8 or 3.1 kernel, the story is the same: no Bluetooth and no WiFi. The 3.0.8 will need to be made compatible with CM10, but making WiFi and Bluetooth work will still won't be easy. That's why it is better to work on 3.1 kernel when you know that both kernels have the same story.
I hope you understand.
My phone is not dead!!!!!!!!!!!
Ok i understand that wifi and bt do not work with 3.0.8 and cm10, but blefish said in one thread that it is just a matter of configuration and is not nearly as hard as making a new kernel. I think blefish could make it work with 3.0.8.
Sent from my Nexus 4 using xda app-developers app
alexmbra said:
My phone is not dead!!!!!!!!!!!
Click to expand...
Click to collapse
That's the spirit!!
rastek said:
Ok i understand that wifi and bt do not work with 3.0.8 and cm10, but blefish said in one thread that it is just a matter of configuration and is not nearly as hard as making a new kernel. I think blefish could make it work with 3.0.8.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Yes, it is a matter of configuration.
All we have right now are the drivers from Aurora and the drivers from official Huawei ROMs. To make CM10, the drivers need to be taken from an older ROM and put into CM10. Now, it is not just a matter of copy-pasting. Our current drivers are not compatible with JB. Blefish has made some things working. The biggest problem is the WiFi. The old WiFi drivers need to be made compatible with CM10, and this is the hardest part. This is why there has been no one, yet, who has been able to do this.
No matter what kernel it is, may it be 3.0.8 or 3.1, the WiFi drivers need to be made compatible with CM10.
I think oguzhan mobile was able to fix the WiFi to the extent where it actually turned on, but it wouldn't scan. I don't know why he stopped development. I am not sure what kernel oguzhan mobile was using, but I think it was 3.0.8. I think you might be right that it would be easier for our phone to use the 3.0.8 kernel, but I think the 3.1 kernel would run better with CM10.1.
If you really want to know why Blefish wouldn't use 3.0.8 kernel, then you would need to Blefish himself. I have already said what I think, but I am not sure if I am right.
I am going to give it a try with 3.0.8 kernel. It might be easier than 3.1 kernel. I'll just have to find out
I like the way you talk....
Waiting for JB...
Sent from my U8800 using Tapatalk 2
Just follow @rtammekivi on Twitter if you want to know what's going on.
Phone is dead
Hi guys,
I am trying to develop ROMs for Android. And I have developed one. This ROM is based on the stock HTC One ROM. Getting straight to the point, I need some Beta-Testers as I don't have the device with me. Sure, I'm gonna buy it soon. But in the meantime, I don't want to waste my precious time. SO< ANYONE INTERESTED? :highfive:
Thanks in advance.
Blind builds like what you did are not encouraged because it magnifies the chances of things to go wrong since you can't test the ROM yourself. Just a not of caution
pandaball said:
Blind builds like what you did are not encouraged because it magnifies the chances of things to go wrong since you can't test the ROM yourself. Just a not of caution
Click to expand...
Click to collapse
yea. I know it is a blind build, but I didn't really do any huge modifications. Just some changes here and there. I have the build ready with me. I just need a guy to tell me surely that this build is safe to work upon further. That's because I am gonna resort to android development in future.
Short of sounding like a D-bag, what you're asking for is a little ridiculous. You sound like you're new to developing, new to the boards (Welcome btw) and don't have the device yourself. Its like asking a random person to test drive a car you just built by reading a "Build-it-yourself Car". If you had more credibility, i.e. More posts, past work, past examples of ROMs or even a list of what was "modified" in this ROM, people might step up to help.
V2IBH2V said:
Hi guys,
I am trying to develop ROMs for Android. And I have developed one. This ROM is based on the stock HTC One ROM. Getting straight to the point, I need some Beta-Testers as I don't have the device with me. Sure, I'm gonna buy it soon. But in the meantime, I don't want to waste my precious time. SO< ANYONE INTERESTED? :highfive:
Thanks in advance.
Click to expand...
Click to collapse
what's so different with your rom and the roms already out ?
ant78 said:
what's so different with your rom and the roms already out ?
Click to expand...
Click to collapse
Everyone's gotta start somewhere, even just doing this is good practice for him.
I'd test for ya op but I rely heavily on this phone and I'm s off. I'd advise any testers to be s on just to be extra safe
Sent from my Tricked out HTC One
Squirrel1620 said:
Everyone's gotta start somewhere, even just doing this is good practice for him.
I'd test for ya op but I rely heavily on this phone and I'm s off. I'd advise any testers to be s on just to be extra safe
Sent from my Tricked out HTC One
Click to expand...
Click to collapse
I do agree you have to start somewhere. But he should get his own device and test it himself. That is better than just creating something that you don't even know it works.
Some "experienced" developers sometimes don't even own the device to create a custom ROM. But the key is that they are already experienced and would know how things work. But for someone who is starting out and have very little experience, they are better off doing the tesing themselves.
I bet he is not really a dev but more like a zip dev if you know what I mean.
OP.. please understand. Your new here, you have no proven track record, your asking people to entrust a €600 device to something that you have 1. not clearly laid out in your opening post 2. have no means to test yourself 3. can not provide support if you feck up other peoples devices.
Sorry but without any past experience here your trust level is 0.
Your request is akin to a nigerian ringing me and telling me I've won a multi-million € win and all they need is my bank account, and credit card info....
At least stick around here, get the device yourself, build up your reputation, and try a few things yourself and then clearly lay out what you have done in any further thread requesting testers because blind faith only goes so far......... unless you are indeed Jesus (or a nigerian with my mulit-million pound win)...
Wow.. so we can't waste his precious time. Lol
Sent from my HTC One using Tapatalk 2
Hey hey hey! Please don't classify me as a ZIP dev..!
N yeah. Here's the change-log of my ROM(though it's not much):
1. Rooted
2. Busy-box added.
3. Changed the boot-animation a bit.
4. changed the power down animation a bit.
And' thats all.
V2IBH2V said:
Hey hey hey! Please don't classify me as a ZIP dev..!
N yeah. Here's the change-log of my ROM(though it's not much):
1. Rooted
2. Busy-box added.
3. Changed the boot-animation a bit.
4. changed the power down animation a bit.
And' thats all.
Click to expand...
Click to collapse
I think everyone has to start somewhere, but I think the people are looking at stuff like what did you change in functionality not just cosmetics. Try playing around with build prop and stuff
Sent from my HTC One using xda premium
Android The Greek said:
I think everyone has to start somewhere, but I think the people are looking at stuff like what did you change in functionality not just cosmetics. Try playing around with build prop and stuff
Sent from my HTC One using xda premium
Click to expand...
Click to collapse
Yeah, sure. I would work on this ROM further. But somebody has to test this adolescent ROM first, because it could happen that I work upon this ROM without testing it and then it would happen that it won't work. And then I could have to roll-back, only to start from scratch.
And that is why I'm asking you guys to test this out. I guarantee regular updates, fixes, etc.