Related
Hello all,
This post is meant so we can get to know each other before the dev community gets going. This way we learn what each other's strengths are and can maybe get things going better.
My name is Chuck and I am a well versed XDAer. I came from the HTC Wizard and WinMo and then moved on to the G1. There I learned from guys like JF, Haykuro and, everyone's hero, Cyanogen. I didn't really do any devving there though. I then moved on to the Hero and since we didn't really have any devs I stepped up and learned how to cook roms. Then I learned how to compile AOSP and kernels. I built the Gutted Hero rom, which I eventually abandoned due to time restraints but I know that won't happen here. I am attempting to learn more about linux exploits and gaining root so that hopefully I can help root this beautiful device when it comes today.
So anyone else who wants to please join in and let us know your background.
Hi Chuck!
I'm pretty much a n00b when it comes to the dev environment, but I want to jump in and get my hands dirty I started reading XDA back when the HTC Titan (Mogul) first hit the scenes, but then jumped into a Blackberry... Since jumping, I haven't really looked back into wanting to learn until news of Android... Then mentions of the HTC "Supersonic" coming to a CDMA carrier (I have Sprint btw) and as well as the N1 possibly releasing a CDMA version. That caught my attention and now I really want to learn and jump into developing!
Now I'm trying to read up as much from the different Android forums, but it's all so much... Trying to take it one step at a time. I'm not a complete n00b when technology is involved, as I used to build boxes back in the day of Pentium II/III, AMD T-Bird days, PC Tech for Gateway (when they had stores), and the sorts...
Stinks that the N1 is not coming to Sprint, but I am planning on getting the Evo. Definately wanting and willing to learn as much as I can!
admin over at SDX-developers.com
wrote my own root exploit for the samsung moment on android 2.1
modified/tweaked an open source recovery
with released open source linux kernel 2.6.27 and 2.6.29, compiled many custom kernels
strong suite, linux. decent with java. terrible with being creative like theming.
excited to work together on the EVO!
edit: for those interested - my android 2.1 resume all with the Samsung Moment
Root Exploit for Android 2.1
Online Kitchen
Linux 2.6.29 Android 2.1 Custom Kernel
Hey guys,
Ok, i have background what so ever... But im slowly learning java so i can start coding and so on with android. So basically my cup is empty...
just wanted to say hi !
Oh and another thing i wanted to add, I was always the guy that devs get files and stuff to for testing and made guides on how to install things and so on ^.^
side note
Themer
Well this is a nice way to meet each other and see what we can assist each other with. I began with editing files, back in the Apache the small fridge looking device . I've been in the windows scene for about 3-5 yrs or so and modded, and mostly created themes. In that time frameI learned to edit manila files,make cabs, and learned how to edit all different software ui apps, windows, and shell. The Vogue had the android files arranged and worked with to use in the sdcard and have the android working with it working I found out how to edit files and do some soft modding. I then learned how to theme but with family and biz I've still got the need to sit down and learn to package, and the rest of the guru qualities as some of you may have. Here is a thread I've begun as I did with the Hero for all creations, mods, themes etc to be shared. I've enjoyed learning and being a part of XDA, looking forward to the fellowship. I've begun editing the Evo files and created some clock's and will continue with rosie, taskbar and apk's you can view it here: http://forum.xda-developers.com/showthread.php?t=685537
Apache-Mogul-Vogue Touch-TouchPro-Hero-Evo soon
Thanks to you all that played a part in rooting, roms, modding and making it possible for themers to give it a touch of class to share with everyone as you have with your work.. Thank you
Good idea for a thread.
I'm Justin--but it's easier to go by Shidell--and I'm moving over from the Vogue community. Within the last two years I've gotten serious about development, and have a strong .NET background with a (growing) C/C++ background. However, linux is still pretty foreign to me, which makes development on that platform somewhat challenging.
With the Vogue, I compiled my own build of Eclair for it from AOSP, and worked with Dzo, mssmison, jnadke (and others, all the names evade me right now) on updating/fixing the GPS library.
I'm fairly clueless when it comes to the bootloader, the kernel, how one would go about exploiting either to achieve root (or even how to go about doing so), but I'm eager to learn and help.
I plan on keeping my Vogue and continuing to learn by using that as a test device for more serious ambitions (kernel development/flashing, etc.) But I'll be actively involved in this community as well. Please feel free to ping me with questions, requests for assistance, etc.
(Also, I do have an Evo via Google I/O, so if you're looking for data a bit early, I'd be glad to help.)
Hello all- I have no experience with this stuff at all other rooting & running different roms/hacks on my former devices (g1 & mt3g) so I was debating whether to even post this here...however I am very interested in learning as much as I can about everything mentioned above & more- it is fascinating to me!
So any suggestions on where to start learning (books/links/etc)?
6/4/10 can't get get here soon enough!
tester here
i am willing to begin testing you may send me a pm and we can discuss over gtalk.
i have years of experience of flashing my phone numerous times back in the ppc6700 days and have had a moment since january and always flashing off sdx and am glad to be back on xda! hit me up ill work with you and tell you what bugs i find etc after i know your phone wasnt bricked
Hello, im a loyal follower of joeykrim from sdx-developers. No experience in writing or creating, but MORE than willing to be a test dummy, guide writer, as i can be quite explicit (the good kind), or a noob helper. pm me and i can get you my email address, phone number, or we can chat through facebook. not currently using any other methods of communication but im willing to switch to anything else more universally accepted by these fine forums.
EDIT: joined xda because the evo is coming out, and i hear this is THE place for htc devices. want to give all the assistance i can
My name is Dan, though I also go by Q. I got an EVO at Google I/O, and want to get it rooted while I still can (an NDA may get in the way soon)
I've been hacking on Linux for 8 years now, and know the entire system very well. I'm also not particularly afraid to solder (which is unfortunate, because I'm also not particularly good at it), so that may be an option. I also have a Droid and a Google ION.
I'm a jack-of-all-trades. I know some C, mediocre C++, C# expert, some java (easy to pick up), php, vb.net, etc. I know hardware, but not embedded stuff. I'm the geek that other computer geeks come to. You get the idea.
But, what skills are you using to modify the Android kernel? Do I need to know assembly? C++? I know I need to know C and the Linux kernel, but how much of the kernel do I need to know? Beginner, so-so, professional, expert? Do I need to know embedded Linux specifically? Do I need to know Linux drivers?
Just point me into the right direction, thanks!
I currently have the G1 from 2 years ago. I'm put my deposit down, and getting my EVO on 6/4/2010. I look forward to learning from you guys.
im well... toastcfh been through a lot with linux for sure. it all started with my old Dell Axim X50. i began working on linux for that device before android was a real deal. then i got a HTC Diamond and did a lot of kernel work for the support of linux on it and other HTC devices. got my HTC Heroc by a streak of luck and smooth talking for free (sprint can be dumb) . anyhow, on the Heroc i managed to be a big part of root,porting and development for it. the main things im known for is my work on Eclair for the Heroc and more recently my port of Eris 2.6.29 kernel source to the Heroc. creating my own board files through a lot of creative debugging and previous struggles with backporting drivers from .29 to .27. at the moment its the only .29 source for the Heroc as Sprint/HTC hasnt even released the .29 source for the device yet. also my work with overclocking the Heroc, but those are just notable contributions to the community ive made. im also the kind of person that is willing to help almost anyone. ask anyone whose ever asked for my help. i believe in the idea of open source and helping others. i also believe in giving credit where credit is due. or at least giving it the boyscout effort anyhow i cant promise ill be ablee to make ur EVO turn into a skynet and cleanup the oil spill in the Gulf. but i can promise that ill damn sure try. im not one to be told it cant be done, nor will i ever except that statement unless it can be proven without a shadow of a doubt (btw its pretty hard to prove to me )
anyhow im looking forward to root, as we need that first and for most. im happy to know we got some awesome devs here and coming soon.
as a single developer i am nothing. but together we can have everything.
toastcfh said:
im well... toastcfh been through a lot with linux for sure. it all started with my old Dell Axim X50. i began working on linux for that device before android was a real deal. then i got a HTC Diamond and did a lot of kernel work for the support of linux on it and other HTC devices. got my HTC Heroc by a streak of luck and smooth talking for free (sprint can be dumb) . anyhow, on the Heroc i managed to be a big part of root,porting and development for it. the main things im known for is my work on Eclair for the Heroc and more recently my port of Eris 2.6.29 kernel source to the Heroc. creating my own board files through a lot of creative debugging and previous struggles with backporting drivers from .29 to .27. at the moment its the only .29 source for the Heroc as Sprint/HTC hasnt even released the .29 source for the device yet. also my work with overclocking the Heroc, but those are just notable contributions to the community ive made. im also the kind of person that is willing to help almost anyone. ask anyone whose ever asked for my help. i believe in the idea of open source and helping others. i also believe in giving credit where credit is due. or at least giving it the boyscout effort anyhow i cant promise ill be ablee to make ur EVO turn into a skynet and cleanup the oil spill in the Gulf. but i can promise that ill damn sure try. im not one to be told it cant be done, nor will i ever except that statement unless it can be proven without a shadow of a doubt (btw its pretty hard to prove to me )
anyhow im looking forward to root, as we need that first and for most. im happy to know we got some awesome devs here and coming soon.
as a single developer i am nothing. but together we can have everything.
Click to expand...
Click to collapse
yes! youre getting an evo 4g! we're going to have a nice group of devs here ..i having a feeling toast is going to be the one to port froyo
Cheers to all the great devs speaking out. I've been watching the android game from the sidelines since the G1... I've been a palm loyalist for the longest time, but I'm finally dropping the Pre to jump onthe EVO.
Can't wait to get into customs roms (bleh to Sense, hoping for vanilla froyo).
I'll be everyone's testpig, I promise
Hey guys, I'm Kyle. Currently a computer science major at Berkeley. I haven't really messed around with Android before, but I attended I/O and received an Evo. I really want to get this thing rooted, but I have no idea where to even start. If anybody has some pointers, that would be great.
Happy hacking
Adam / apristel - Live in Green Bay, WI, 15yr computer tech, mostly windoze and linux.
Started phone hacking when the RAZR came out. I helped get modmymoto.com going and spent alot of time being a mod there. I also created some very popular roms aka monsterpacks for the GSM V3 RAZR, then moved to the V6 MAXX....few years later got onto the WM Scene, got a TP and eventually a TP2. I made personal roms, never shared them, but I shared tons of hacks and cabs I made. I got sick of WM and got a moment and a hero. ..now the EVO in a few days.
I'm willing to put in what I can, I know I'm not at the level of you linux pro's but I'm not scared to try anything.
Glad to see familiar names here - this should be an exciting time. Glad to share it with you fellas.
Welcome me in!
I've done a lot of themes for HTC devices throughout the years. I've owned mainly windows mobile devices, such as i930, Apache, Titan, Touch Diamond, Touch Pro, and the Touch Pro 2. I've always been flashing ROM's and helping ROM dev's with hexing things, changing some layouts here and there, registry edits and of course testing it before it went public. I also host all this stuff online for free since I HATE countdown sites for a download.
I helped with MightyROM themes and we had over 7TB of data pulled from the servers, which is pretty amazing, but I'm all Android now!
I hope to learn Android quickly and hope that some of my tools will also work with it. I have good hosting capabilities if a dev needs it, and I'm more then willing to help. I've done work for over 10+ cooks, on over 8 different devices since 2003.
Background: BSCE, Machine Language on MIPS, x86 / arm / mot / att assembly, C/++ on Posix and Win32. PIC / HC11 system design. GCC cross compiling. Have a JTAG, digital storescope, and an HP protocol analyzer. Been using Linux exclusively at home since '99.
Projects:
- Open source contributor on a few Linux projects (mainly device driver / interface development)
- Helped with the Agenda Vr3 (Snow rom)
- Hacked around with the IPAQ Linux (hardware and software)
- Helped with the Zaurus FBVnc effort
- Helped with the IOpener hack / USB problems
- Helped with the EPOD Windows CE hack / drivers
- Helped with various efforts on the Palm Pre
Future Projects:
- Root (someone will probably beat me to this)
- WebKit over HDMI (not sure where it stands on launch day)
- BT HID Keyboard (sounds like we need some back porting here)
- BT HID Mouse (virgin territory from what I have seen)
- Video recording bitrate (fun project on the side)
The EVO is my first android phone, not my first HTC though. So hopefully I can help a little bit here and there.
Hello,
I work with a small company and develop everything from boards to firmware to full-blown desktop applications for interfacing with different sensors and devices.
I've started at both ends of the computer world and am working my way towards the middle. On one hand I know my way around assembler (although I prefer C...) and write firmware for AVRs and PIC microcontrollers and on the other I'm a fluent .Net developer and have built some pretty complex .Net applications, some PHP applications, and fiddled around with the Google web toolkit.
I've reverse engineered hardware before but nothing close to the complexity of the EVO. I've never developed for Android before but I'm eager to break out the SDK and learn. I have some limited Java experience (my philosophy is once you know one managed language you know them all and I have some extensive experience with it's cousin, C#).
Very eager to start tearing into the EVO and Android system and see if I can't contribute to the effort to root and expand this device!
I've never been a huge contributor to a community effort but I hope to change that in the coming years and see if I can't contribute something back to the communities I have learned so much from!
I'll be getting my EVO June 4th
Relative rookie here in terms of mobile devices. I've put together a few custom WinMo ROMs for co-workers and myself. I've quite a few devices, but currently have the ones in my sig. I'm a professional computer geek. I write apps in C++, various .NET, PHP, etc. and work primarily with server systems (Windows, Linux, Solaris, etc.).
Looking forward to contributing to the Android world soon. Lots of great stuff here.
Hello,
This was brought up in another thread that is now locked.This post asked the question.
http://forum.xda-developers.com/showpost.php?p=11287492&postcount=40
and this is the blog post by Cyanogen
http://www.cyanogenmod.com/home/a-note-on-unofficial-ports-and-how-to-get-it-right
From what I can make from the blog post that Cyanogen put up on the CM website the Epic 4g as well as the other Galaxy S CM ports are not backed by Cyanogen because they do not go through the normal chain of how they add their code into their source code tree.The Galaxy S CM github has many changes to the stock android code that could possible and probably does break the code from being compiled for other phones. The framework is modified to work with the Samsung RIL that our phones use. The CM team will make additions to the stock android code not modifiy the stock code itself. So from my understanding of thing this is why Cyanogen does not consider what the CMSGS team has done as a part of the mainline CM code base. I believe this goes for all the Galaxy S phones not just the Epic.
Does being backed by the CM team make it get done any quicker? If so....
Sent from my SPH-D700 using XDA App
Being backed by the Cm team would definitely speed up the porting process, Cyanogen had the Evo Release Client up and running in a little over a month without source
So its a matter of pulling the source together and prperly placing it into their source control so their build bot can properly dov what build bots do...build...then CM helps with the port process?
If I think I'm following that right...somone better start uploading code to Cyanogens t&c's(terms and conditions) so we can have some epic awesomesauce.
Sent from my SPH-D700 using XDA App
Most importantly, no major hardware functionality should be broken.
Click to expand...
Click to collapse
What this statement implies is that no Cyanogenmod port is ever gonna be official right away; there's always an in-progress period where major functions are broken. Regardless of other issues, that's where our Epic port is at right now and part of the reason why it's not official.
Poryhack said:
What this statement implies is that no Cyanogenmod port is ever gonna be official right away; there's always an in-progress period where major functions are broken. Regardless of other issues, that's where our Epic port is at right now and part of the reason why it's not official.
Click to expand...
Click to collapse
True but there is code that is changed in the Galaxy S port that doesn't get changed at all in other CM ports as far as I know.
If we had HTC Epic's instead of Samsung Epic's and still identical devices... CM would officially support the Epic.
Period. They can say whatever they want but we all know this to be the case. You can't tell me Samsung changes their code that much more then HTC... last I checked Sense was a much more in depth overall to the underlying OS then Touchwiz is.. but maybe not.
The thing is, HTC uses the same hardware across the board (snapdragon processors, same camera etc.) which makes Rom ports much much easier to pull off, whereas the Hummingbird in the Galaxy S is only in the Galaxy S and only the Unlocked Galaxies and Gsm have froyo source so far.
Thanks for osting this skeeter
Android Creative Syndicate- From spontaneous ingenuity, comes creative brilliance
063_XOBX said:
The thing is, HTC uses the same hardware across the board (snapdragon processors, same camera etc.) which makes Rom ports much much easier to pull off, whereas the Hummingbird in the Galaxy S is only in the Galaxy S and only the Unlocked Galaxies and Gsm have froyo source so far.
Click to expand...
Click to collapse
The changes in the code have nothing at all to do with the cpu its all for the radio which even having froyo source will not help a bit with.Its all in the way the code changes were done. Rather then adding to the base code in CM the code was directly changed which is what Cyanogen has an issue with doing so basically could and probably has broken the radio code for other cdma phones, I don't know what or if any of the code in the frameworks was changed for the gsm Galaxy S phones so I can't say for sure that it the source from the CMSGS github wouldn't work on another GSM phone I only know that changes were made to get it working on the Epic and Fascinate.I don't think what the CMSGS team did was wrong they did what they had to do to get things working and from the time I spent working on it it didn't seem like there was much input from the CM team at all but that was probably happening in another irc channel that I was not invited into if they were involved.I was hoping that the Galaxy S would have had more interest from the CM team as a whole I know a phone or two was collected and donated to at least one dev and i also heard that Koush was supposed to take over the Captivate port of CM I am not sure if that ever happened or not but the Epic and Fascinate were from the beginning the red headed step children of the Galaxy S line it really is too bad that there wasn't for developers around to help work on it and make an offical Cyanogen backed CM port.I blame it all on the Evo personally if the Epic came out first it would be the Epic sporting all the kernel and roms that you can find in the Evo forum instead we are left with a handful or less of devs and a phone that is far from the potential that it has.
This statement brings up one of my biggest questions I have for the epic forums that I have yet to understand. If a lack of devs are the biggest problem for the epic why is it they are not attempting to train anyone else. Here's my point. I have cataloged every bit (and still am) of info I know about themeing android and the samsung epic. I wrote guides breaking down every part of installing the tools necessary and using them so anyone just sitting down with a fresh windows and their first android phone would understand. Where are our dev guides besides "read developer.android.com". I've read it, I've set everything up. I've downloaded source, I've even ran make with success. But it does nothing without proprietary files. How do you plug them in. extract files.sh dont work without cm6 running on my phone. Where do we learn how to edit our build.prop, init.rc, compile drivers and modules. Joey krimm it's a great beginners source but what about updates since the stall between ubuntu 10 64 support, and 64 becoming the default. I feel like not only it's sammy and sprint at fault, but so are devs that arent open with their knowledge. The best gift this community could have gotten in all of this "down time"waiting was time spent learning. Devs stuck waiting on modems and source, start writing and teaching so when you get that source, you'll have a team behind you. That's the spirit of linux and it dont exist on xda's Samsung Epic Development section!
Sent from my SPH-D700 using Tapatalk
dreamsforgotten said:
This statement brings up one of my biggest questions I have for the epic forums that I have yet to understand. If a lack of devs are the biggest problem for the epic why is it they are not attempting to train anyone else. Here's my point. I have cataloged every bit (and still am) of info I know about themeing android and the samsung epic. I wrote guides breaking down every part of installing the tools necessary and using them so anyone just sitting down with a fresh windows and their first android phone would understand. Where are our dev guides besides "read developer.android.com". I've read it, I've set everything up. I've downloaded source, I've even ran make with success. But it does nothing without proprietary files. How do you plug them in. extract files.sh dont work without cm6 running on my phone. Where do we learn how to edit our build.prop, init.rc, compile drivers and modules. Joey krimm it's a great beginners source but what about updates since the stall between ubuntu 10 64 support, and 64 becoming the default. I feel like not only it's sammy and sprint at fault, but so are devs that arent open with their knowledge. The best gift this community could have gotten in all of this "down time"waiting was time spent learning. Devs stuck waiting on modems and source, start writing and teaching so when you get that source, you'll have a team behind you. That's the spirit of linux and it dont exist on xda's Samsung Epic Development section!
Sent from my SPH-D700 using Tapatalk
Click to expand...
Click to collapse
Where's the thank spam? hah.
I've slowly been dipping myself into the Developer 'pool' for the epic if you will..and at first when I started working nobody really ever helped out..they just threw me a link and was like..start reading blah blah blah..
Reading only gets you so far; Imho you learn better when you've got the experience of working first hand with the material you're trying to learn.
dreamsforgotten said:
This statement brings up one of my biggest questions I have for the epic forums that I have yet to understand. If a lack of devs are the biggest problem for the epic why is it they are not attempting to train anyone else. Here's my point. I have cataloged every bit (and still am) of info I know about themeing android and the samsung epic. I wrote guides breaking down every part of installing the tools necessary and using them so anyone just sitting down with a fresh windows and their first android phone would understand. Where are our dev guides besides "read developer.android.com". I've read it, I've set everything up. I've downloaded source, I've even ran make with success. But it does nothing without proprietary files. How do you plug them in. extract files.sh dont work without cm6 running on my phone. Where do we learn how to edit our build.prop, init.rc, compile drivers and modules. Joey krimm it's a great beginners source but what about updates since the stall between ubuntu 10 64 support, and 64 becoming the default. I feel like not only it's sammy and sprint at fault, but so are devs that arent open with their knowledge. The best gift this community could have gotten in all of this "down time"waiting was time spent learning. Devs stuck waiting on modems and source, start writing and teaching so when you get that source, you'll have a team behind you. That's the spirit of linux and it dont exist on xda's Samsung Epic Development section!
Sent from my SPH-D700 using Tapatalk
Click to expand...
Click to collapse
When it comes to working on CM most of the work that needs to be done is all coding which we have very few if anyone java coders. Also you can use extract-files.sh on a phone running straight DK28 to get the propietary files needed to build CM with.When it comes to everything else most of the devs have taught themselves how to do the things they so by trial and error and alot of reading the internet. I know I have little coding skill so its would be hard to teach someone something you don't know how to do yourself and alot of the other things like putting togther device files to build android even on the google site has no real information on how to do it at all the best way I think is to just compare what the other phones use and piece it together from that.
Yet it still makes me wonder; why no epic/galaxy s support? Virtually every other phone, and even some tablets like the gtab, have CM support and even CM7 support. Even the HTC Hero, with obviously no source code for 2.2 or 2.3 and no official 2.2 ever to be released, has a working build of CM7. Is it pure incompetence of Epic developers? Is it a lack of interest? Is it simply cyanogen not wanting to support galaxy s devices? I really don't know, but I'd really like to.
theimpaler747 said:
Yet it still makes me wonder; why no epic/galaxy s support? Virtually every other phone, and even some tablets like the gtab, have CM support and even CM7 support. Even the HTC Hero, with obviously no source code for 2.2 or 2.3 and no official 2.2 ever to be released, has a working build of CM7. Is it pure incompetence of Epic developers? Is it a lack of interest? Is it simply cyanogen not wanting to support galaxy s devices? I really don't know, but I'd really like to.
Click to expand...
Click to collapse
From what I can see its not that Cyanogen doesn't want to support the galaxy s devices its that it seems they don't give any input to the devs that are working on CM for the galaxy s. They have basically split off from the main CM source tree itself and run their own source tree. It seemed like (and this is from the limited amount I saw on irc) that there was no input from the CM team they just let them work on their own. CM has ways to setup the code so the source tree remains workable across the board on all the devices it supports, the cmsgs team has just taken a different route on things and gone their own route thus making it not backed by cyanogen, was it the right way to do it who knows but it has made all the galaxy s devices redheaded step children in the eyes of Cyanogen and the CM team as a whole by the looks of it. I know from the point of view of having an Epic the major hold up to it is having coders with the proper skills to do the coding in general we had one coder working on it I don't know if he is still involved or not at this point. All I know is to make is a backed by Cyanogen CM port the coding that has been done so far would have to be completely redone in the ways that the rest of the CM team adds code to the CM source tree with as little to no modification of the stock CM code as possible.
Also I would like to add that I am not trying to put anyone down that is working on the CMSGS team they have done CM working on these devices and am in no way bad mouthing the work that has been done. This is just my view on things and why Cyanogen doesn't back the galaxy s CM ports.
Sent from my SPH-D700 using Tapatalk
theimpaler747 said:
Yet it still makes me wonder; why no epic/galaxy s support? Virtually every other phone, and even some tablets like the gtab, have CM support and even CM7 support. Even the HTC Hero, with obviously no source code for 2.2 or 2.3 and no official 2.2 ever to be released, has a working build of CM7. Is it pure incompetence of Epic developers? Is it a lack of interest? Is it simply cyanogen not wanting to support galaxy s devices? I really don't know, but I'd really like to.
Click to expand...
Click to collapse
Well, trying to comprehend everything that is going on here, I feel like the CMTeam does not feel the Epic is worth porting to CM7 due to it's delay on a FroYo source, which I am positive would make the Epic's porting much easier.
However, it still makes me wonder why they could not have used 2.1 to port to CM7, as like you said, the Hero has been able to do.
It also confuses me that the Captivate has even been able to run a Gingerbread port (I believe cyanogen) then. I realize that the Captivate has no 4G or a slide or anything, but the fact that they were willing to work off of 2.1 I assume gets me wondering why no one has tried making a CM port for the Epic's 2.1
I am trying to understand this as best as I can, so please forgive me if I seem to be giving false input on this conversation.
Its the time taken to port a phone, combined with the number of phones above yours on their list. The fact is they have a list of other phones they feel like investing their time in over the galaxy s line in general which is even more of a reason all knowledge of development on the Epic should be layed out even in pieces like the rest of the information here. Honestly thinking "leak it to noobnl, then we'll get all the goods" isn't going to cut it. Java coders, ubuntu fanatics who have compiled a few apps, and new people willing to learn should be putting heads together compiling new ****. If we dont start a group effort of making a bone stock aosp froyo altering the existing drivers were not going to be much further with source code. And it should be layed out here irc dont work for everyone.
Sent from my SPH-D700 using Tapatalk
acer1096xxx said:
Well, trying to comprehend everything that is going on here, I feel like the CMTeam does not feel the Epic is worth porting to CM7 due to it's delay on a FroYo source, which I am positive would make the Epic's porting much easier.
However, it still makes me wonder why they could not have used 2.1 to port to CM7, as like you said, the Hero has been able to do.
It also confuses me that the Captivate has even been able to run a Gingerbread port (I believe cyanogen) then. I realize that the Captivate has no 4G or a slide or anything, but the fact that they were willing to work off of 2.1 I assume gets me wondering why no one has tried making a CM port for the Epic's 2.1
I am trying to understand this as best as I can, so please forgive me if I seem to be giving false input on this conversation.
Click to expand...
Click to collapse
But like I said, there's CM7 (Android 2.3 if you don't know) for the HTC hero, with no 2.2 or 2.3 source code. So why not us?
theimpaler747 said:
But like I said, there's CM7 (Android 2.3 if you don't know) for the HTC hero, with no 2.2 or 2.3 source code. So why not us?
Click to expand...
Click to collapse
Alright, this is what I believe.
The Hero does not have 4G, or a QWERTY keyboard, two things the Epic does have that could make a pure AOSP port more difficult without a source. Also, HTC runs Snapdragon throughout the whole system, making tweaks a lot more simpler than SGS's Hummingbird Processor, which uses something else (I can't remember) with their system as well.
The last part I'm not sure if that makes a big deal or not, since I have seen a (what I think) CM7 port for the Samsung Captivate, so it may simply be because of 4G and the QWERTY keyboard.
I see what you're saying though. I guess the CMTeam should have no problem making a CM7 port based off of the Epic's 2.1 source...maybe they're just waiting because 2.2 might make it easier and supposedly 2.2 is coming soon so there'd be no point in starting now...otherwise I have no clue.
acer1096xxx said:
Alright, this is what I believe.
The Hero does not have 4G, or a QWERTY keyboard, two things the Epic does have that could make a pure AOSP port more difficult without a source. Also, HTC runs Snapdragon throughout the whole system, making tweaks a lot more simpler than SGS's Hummingbird Processor, which uses something else (I can't remember) with their system as well.
The last part I'm not sure if that makes a big deal or not, since I have seen a (what I think) CM7 port for the Samsung Captivate, so it may simply be because of 4G and the QWERTY keyboard.
I see what you're saying though. I guess the CMTeam should have no problem making a CM7 port based off of the Epic's 2.1 source...maybe they're just waiting because 2.2 might make it easier and supposedly 2.2 is coming soon so there'd be no point in starting now...otherwise I have no clue.
Click to expand...
Click to collapse
I think we also have 'limited functionality' w/ 2.1 as far as the phone's full capability.
2.2 will unlock some hidden potential IMO. Could be the reason why all the hubbub to 'wait for 2.2'.. again, just speculating.
Cornerstone is a way of enabling multi panel multitasking on android tablets. To see what i'm going on about, go here http://www.onskreen.com/cornerstone/.
Basically, Onskreen have just made cornerstone open source. I was hoping that a dev, who is more capable than i am, with my limited knowledge of android would be willing to compile a rom with cornerstone in it.
The github can be found here https://github.com/Onskreen/cornerstone.
I am not by any means demanding a dev take up this project, i have no right to do so. I just think this would be a valuable addition to our vega's!.
Thank you in advance to anyone who makes an effort to bring cornerstone to the vega
2 days later...
... and BAM!
http://android.modaco.com/page/news/_/android/windowed-multitasking-may-be-coming-to-cm9-r320
This might be integrated in CM9 and will therefore be automatically in VegaICS ROM.
I hope you liked that news!
vegaics is not a cm9 build. Therefore it won't automatically be added.
Sent from my Desire using XDA App
This would truly be epic if we could get this built into either the ICS or honeycomb builds, I think it would make our tablets significantly more useful!
Anyone who knows what they are doing care to take a look
Boot to Gecko is coming! if you haven't heard of b2g, its a web based replacement OS designed to take on android, apple and WP7, the exciting thing is, to speed up the release, it is relying on similar linux based processes to run. see here ;
https://wiki.mozilla.org/B2G
I'm in no way associated with this project, just wanted you guys to see it. Some industrious developers are already working at a port for the galaxy s2 and the nexus. I know we have talented dev's right here, can we be far behind?
exciting yes??!!
Ava.tar said:
Boot to Gecko is coming! if you haven't heard of b2g, its a web based replacement OS designed to take on android, apple and WP7, the exciting thing is, to speed up the release, it is relying on similar linux based processes to run. see here ;
https://wiki.mozilla.org/B2G
I'm in no way associated with this project, just wanted you guys to see it. Some industrious developers are already working at a port for the galaxy s2 and the nexus. I know we have talented dev's right here, can we be far behind?
exciting yes??!!
Click to expand...
Click to collapse
Yeah, true, we really have quite wonderful devs for our G3 community, it shall just be a matter of time, I think
I'm pretty sure that rubbensolie will look forward to boot gecko to our phone ;P
Darius_AWS said:
I'm pretty sure that rubbensolie will look forward to boot gecko to our phone ;P
Click to expand...
Click to collapse
I already did look into it actually xD. But no progress, because i think we need another kernel for it.
Ava.tar said:
Boot to Gecko is coming! if you haven't heard of b2g, its a web based replacement OS designed to take on android, apple and WP7, the exciting thing is, to speed up the release, it is relying on similar linux based processes to run. see here ;
https://wiki.mozilla.org/B2G
I'm in no way associated with this project, just wanted you guys to see it. Some industrious developers are already working at a port for the galaxy s2 and the nexus. I know we have talented dev's right here, can we be far behind?
exciting yes??!!
Click to expand...
Click to collapse
As it is not a different Android version, but a totally different system, it will require developing a new kernel, whole new drivers and of course porting the system.
Kernel and driver developing are much a pain in the a*s, so it won't be "easy" like porting MIUI (i do not mean to offend anyone).
I think it will require months of hard work from a c/c++ skilled dev....
Of course, i would be more than happy if someone is able to state the opposite!
I did a bit more poking around and found that mozilla marketplace (the boot to gecko play store) is now open to devs!
Admittedly this wont be an easy port but the similarities between b2g and android will surely put our devs here ahead of the pack in the race to port b2g. And they are already having a good try on other android devices. I have so much faith in our devs!
https://marketplace.mozilla.org/en-US/login?to=/en-US/developers/
Heres the link
Well, i know how to develop web apps but i don't get the point on mozilla choice...
And performances of webapps in mobile phones are VERY low. I mean REALLY VERY low. At least, they are low until you provide optimized code for the underlying hardware but if you do so, you will need to provide a different interface for every kinf od hardware, ie: you will need to build a kernel with proper dirvers...
I'm not saying it can't be done, of course it can be, but as i stated before, it will be a major work from a skilled dev.
From my point of view, having CM7 /and then 9) fully working is much more interesting than trying to port mozilla OS.
andreapier said:
Well, i know how to develop web apps but i don't get the point on mozilla choice...
And performances of webapps in mobile phones are VERY low. I mean REALLY VERY low. At least, they are low until you provide optimized code for the underlying hardware but if you do so, you will need to provide a different interface for every kinf od hardware, ie: you will need to build a kernel with proper dirvers...
I'm not saying it can't be done, of course it can be, but as i stated before, it will be a major work from a skilled dev.
From my point of view, having CM7 /and then 9) fully working is much more interesting than trying to port mozilla OS.
Click to expand...
Click to collapse
Well looking at the work already being done it doesnt look slow, it looks blazing fast! the interface looks brilliant and incredibly user friendly. I am pretty excited about a finished cm9 too but chasing released android firmwares to port is surely not as fun for talented devs as getting in on something at ground level? this isnt even out yet! its not even a blip on apple or androids radar, it is exciting!
its just another option. Im sure it will be something being discussed more and more in the very near future
Updates
https://wiki.mozilla.org/Gaia/Hacking
http://ftp.mozilla.org/pub/mozilla.org/b2g/nightly/latest-mozilla-central/
Very exited about this project. Even if takes a year to get it working on our phones.
In my opinion I don't think you should over work devs because they work in their own time and users expect them to be robots who just port roms and develop day and night. Let our devs work on their current projects and finish them to a high standard. Its quality over quantity right?
I don't mean to offend anyone. Just voicing my opinion.
Sent from my GT-I5800 using xda app-developers app
Hello Guys,
welcome to the world of Team-Exodus.
What is Team-Exodus ?
We are a small group of entusiasts that like to learn more about Android and the Android-ROM developement.
We aren't exactly beginners But there is still room to learn more (you never end learning).
What is Exodus-Rom ?
Maybe, we better should start, what Exodus-Rom isn't: It isn't a (semi)professional mainstream ROM like CyanogenMod,AOKP or similar Roms. We don't focus on buzzword features, nor are we into "bling bling" options. We don't need a "change clock color" option, just because we can do it. These are "low hanging fruits", something nearly everybody can do, who has a computer to compile Android.
So what is Exodus-Rom, what is our focus on ?
We mainly focus on learning how things can be done. We are more into "quality over quantity". We prefer to have 4 or 5 real good and stable working features and not 20-30 features that work... somehow... sometimes...
We want performance, a fast, smooth fluid UI, a real good user experience, not a overbloated kang rom.
For instant that's the main reason why we currently don't have a Marshmallow Rom online, but I will give you a little more information regarding Exodus-6.0 (marshmallow) later.
But before that, who are we, who is "Team-Exodus" ?
The core team of "Team-Exodus" consists of the following guys:
@PrimeDirective - Dave, a very talented developer from the US, founder and Team Leader of Team-Exodus, specialist in App developement (for instant our Exodus Updater or the Drop Wallpaper App) and also our specialist for in deep functionalities of the Android Rom (like a complete rewritten Navbar customization). He currently uses bacon (Oneplus One) and Flounder (Nexus 9) for developenemt
@Raja.M - Raja, a real nice guy from India, he is our java specialist, he started Android developement something link 6 month ago but his knowledge is fast growing. He developes on the bacon (Oneplus One)
@TheCrazyLex - Alex, a kernel specialist from germany, he joined Team-Exodus like 3 month ago, mainly responsible to optimize and unify our kernels where possible. He also uses the Bacon (Oneplus One) as developement device.
@usmcamgrimm - Adrian, our graphics and theme specialist. Beside his amazing wallpapers, he is also responsible for all our LGE G3 devices. He mainly developes on the VS985.
@Martin_Ro - myself, Martin, also from germany, mostly responsible for the server with the build system, gerrit and download page. I'm also developing here and there if I find some time as I'm a married guy with to young boys. I'm developing on shamu (Nexus 6).
But beside this core team, there are a lot more ppl that help us making the Exodus Rom as amazing as possible, I will add some more of them step by step
So, now, back to Marshmallow and why it takes so much more time to bring an Exodus-6.0 to you guys:
For this to understand, you need to know more about where we come from.
On late 2014 we (Dave and Me) parted from VanirAOSP (that wasn't really AOSP but also used CM as base at that time btw) because we feeled like it started to get more and more into that mainstream "feature count is everything".
With 5.1 we started to directly use CyanogenMod (cm-12.1) as base, but was somewhat annoyed by upcomming issues because they used their open source branch as testfield for unfinished stuff, so for 6.0 we decided to go as near as possible back to strict AOSP.
But a matter of fact is: With strict AOSP you aren't able to support every device, and not as many devices as we want to support. So we have had to make some decisions and try some stuff. In the end we started developing Exodus-6.0 with a Mixture of strict AOSP and CAF as base, with the really amazing wide support of CyanogenMod regarding devices.
But with this, we got back to one of our main concerns: CyanogenMod is doing a fantastic job regarding device support (nobody can beat them in that department) but they are cluttering their stuff more and more. In the past few month, they started to create their own SDK, their own framework. And their SDK started to grow like a octupus, sticking his arms into every aspect of android. But we don't want to use their sdk, so we needed to remove it from everywhere.
And that was, what took so long. We wanted the device-tree and their hardware layer, but not their feature, and for sure not their SDK. And removing that stuff from everywhere inside the device-trees and Hardware layer.
Also we needed to use some of their code stuff in various places to make the connection between our AOSP/CAF based ROM and their hardware/device stuff.
So that took us nearly a month to finish up, but now we have first working experimental builds for bacon, shamu and VS985 so we can go into the real developing stuff.
There is still a lot to do (bring back all the features we want to, make the rom that fluid that you might be used to from EXODUS-5.1 etc.) But the real hard part is done now and we are way neared to a first public beta. Depending on the time Dave can find for Exodus (he is really really busy currently because of a new job), we expect to have a public beta by the end of the month...
So stay tuned and be patient
Made sticky
Hello! I enjoyed the 1/2 of the core team's and the new teams work since JB VanirAOSP to Exodus .
Just wondering, it would be cool to say what you do to seperate you guys from the rest. I know you guys build with jdk8 instead of jdk7 for the lollipop builds and use Linaro with some optimization flags.
I'd like to know if you do more than that and also I am wondering how JDK8 especially helps with optimization.
If you need a tester for bacon. I'm here very big fan of 5.1.
Nice to hear the updates... waiting patiently...
Sounds like the beta will become a christmas present.
Gesendet von meinem Nexus 5 mit Tapatalk
big fan/user of Exodus 5.1 on falcon. out of all the LP ROMs i've tried this has to be one of the most stable and lean ROMs out there. love the amount of essential customization catered here and skipping of cliche features that no one bothers to use (atleast me).
big thanks to @sachoosaini for introducing me to the ROM.
Well here it goes on
@PrimeDirective always a great human and great developer who supported Falcon despite the fact that i can never able to contribute the device to you. I find a best buddy out there who will always be my friend... Now @koshikas thanks Dave for supporting this phone, i never did anything for exodus.. But i am committed for future. If Dave continues the journey for exodus i will be with him in all way... Well what he told me around 6-7 months back is now coming to the real world. Now they support falcon or not. But I am honored by Dave for being there with all the silly questions people ask in community, falcon has great life indeed now its upto the team they develope for it not. I will donating device as soon as I am getting my salary which i am for sure going to get soon..... Wish Luck to exodus....6.0 is on the horizon
If you need a tester...
Hey, if you guys need an experienced tester for bacon, look no further. :good:
AndroidPr0 said:
Hey, if you guys need an experienced tester for bacon, look no further. :good:
Click to expand...
Click to collapse
I'm with this guy
Where do I go to look at the rims ?....dir a HTC m8 Sprint
With S-on
Coolkid90 said:
Where do I go to look at the rims ?....dir a HTC m8 Sprint
With S-on
Click to expand...
Click to collapse
Hm, ok, might be, because english is not my mother language, but for me this sound like "too much drugs and not enough sleep"....
Oh, and by the way:
we just prepared the open source manifest so you can start contribute
I will write a short Facts thread for Exodus-6.0 so you know how to build, and what we changed regarding device-support...
Excelente
Looking real forward to Exodus MM!
sir I am with you here.
AndroidPr0 said:
Hey, if you guys need an experienced tester for bacon, look no further. :good:
Click to expand...
Click to collapse
I m new here and wish to get some knowledge from senior member.
Thanks for this great rom
Exodus seems cool... hyped for MM release!
delete : found it
"err on the side of kindness"
Hi guys
Only to keep you informed: We started publishing official release builds for Exodus-6.0.
Look into your devide Android Developement sections for more information or on our g+ community: https://plus.google.com/communities/106801227383087889476