[DU][DEV]Developers Unite- The future of DX Development
- Thread starter //.dax
- Start date
I'm in!
I can contribute with testing , debugging , logcatting etc . Plenty of experience from when I had a Galaxy Mini 2 which was in a development stage worse than the DX . (and now it's got a fully working CM10.1 XD) as well as some programming help - I know Android app development , I know a good load of C / C++ , C# , I can read and tweak Java code . I know the Android workflow pretty well , and I'm also an algorythmic whizz if that would ever be of help xD
Internet speed : about 6MB/s down & 2MB/s up .
Availability : I can go all out this week . Starting next week though I'm starting hi-school , but I can still dedicate about 6h / day to the development nonetheless .
Also , a littbe bit of OT (kinda) : I'm planning to get myself a new laptop soon and will dualboot Ubuntu w/ Windows on it , thus I also wanna start learning the linux kernel (only for Android development atm) . If anyone can point me to some baby steps to get me started on that , I would be grateful. I'm not a newb , I learn pretty fast considering I have about 4 years of programming experience . I just need to have a starting point and good documentation along the way
here is where u can start learning
http://xdaforums.com/showthread.php?t=1748297Wow that response was totally unexpected! I never knew that we had so many people in our forum
Anyways, seems like all of you agreed with me so just enter your details in this spreadsheet
https://docs.google.com/spreadsheet/ccc?key=0AjP8Bz9PKaF3dHJyckc2dDdNX3F5allGQjA1U0J4Nmc&usp=sharing
This is will help us in dividing the work. As far as a IRC is concerned.. we need a place where we can chat and it should also get recorded for those who weren't there . I think whatsapp can serve this purpose . Its really helpful for development.. whatta say?? Dont worry, numbers wont be leaked or used for spamming purposes(or you will be blocked)
Anyways, seems like all of you agreed with me so just enter your details in this spreadsheet
https://docs.google.com/spreadsheet/ccc?key=0AjP8Bz9PKaF3dHJyckc2dDdNX3F5allGQjA1U0J4Nmc&usp=sharing
This is will help us in dividing the work. As far as a IRC is concerned.. we need a place where we can chat and it should also get recorded for those who weren't there . I think whatsapp can serve this purpose . Its really helpful for development.. whatta say?? Dont worry, numbers wont be leaked or used for spamming purposes(or you will be blocked)
I offered my help:
I'm I.T. Student, part of my future disertation will be Android.
Fast (actually very fast) internet I have:
Good PC, I have that too:
fill my spreadsheet linked above
Me too..
And whatsapp would be awesome.
Sent from my HTC Desire X using xda app-developers app
With some help how to get started I can do some CM builds as well. I am not an android expert, but I know much about linux, if that can be of help.
I've got good internet speed as well (50 Mbit/s down, 2,5 Mbit/s up).
But I don't have much time, kind of one hour each day.
I've got good internet speed as well (50 Mbit/s down, 2,5 Mbit/s up).
But I don't have much time, kind of one hour each day.
@prototype-U
you might wanna keep the team selective. People learning from scratch wont be able to fix the bugs. And they can always contribute whenver they want by using the git trees.
What i would like is that a team of 3 or 4 people do this.
member "A" for compiling and uploading builds (fast PC and Net)
2 members "B & C" trying various methods on different branches of same repo to fix bugs
1 member "D" to download the latest build uploaded by A, test stuff, post logcat and done...
A is COMPILER/UPLOADER (requires fast PC, NET, and knowlegde to JUST COMPILE ROM)
B & C should be able to analyze the device/vendor/kernel trees to perform debugging. (prototype-U fits in here)
D should be a General guy knowing flashing and debugging/logcat/adb/fastboot/dmsg etc.
This compact team of 4 will be MUCH more efficient with properly defined roles, rather than an army of untrained, learning soldiers.
Just my view, no offence meant for anyone.
you might wanna keep the team selective. People learning from scratch wont be able to fix the bugs. And they can always contribute whenver they want by using the git trees.
What i would like is that a team of 3 or 4 people do this.
member "A" for compiling and uploading builds (fast PC and Net)
2 members "B & C" trying various methods on different branches of same repo to fix bugs
1 member "D" to download the latest build uploaded by A, test stuff, post logcat and done...
A is COMPILER/UPLOADER (requires fast PC, NET, and knowlegde to JUST COMPILE ROM)
B & C should be able to analyze the device/vendor/kernel trees to perform debugging. (prototype-U fits in here)
D should be a General guy knowing flashing and debugging/logcat/adb/fastboot/dmsg etc.
This compact team of 4 will be MUCH more efficient with properly defined roles, rather than an army of untrained, learning soldiers.
Just my view, no offence meant for anyone.
Last edited:
WhatsApp doesn't work on PC , and I think it would be quite troublesome to work on the PC and chat from the phone .
Facebook is a great alternative , but not everyone is eager to join a group due to fear of exposing their privacy . Or maybe not everyone's got a Facebook .
Google Hangouts can be a possible alternative , because if you own a droid , you own a Google account , but then again it uses Google+ so the privacy issue is present here as well .
I'll let you know if I find anything better >.<
@ neXus PRIME : I agree , but one more thing : have a solid team built , but make every new build downloadable by everyone . Don't keep it private . If people want to flash them on their own and try to help , why shouldn't they? Maybe they'll run into some stuff in the logcat that the main team won't see
Facebook is a great alternative , but not everyone is eager to join a group due to fear of exposing their privacy . Or maybe not everyone's got a Facebook .
Google Hangouts can be a possible alternative , because if you own a droid , you own a Google account , but then again it uses Google+ so the privacy issue is present here as well .
I'll let you know if I find anything better >.<
@ neXus PRIME : I agree , but one more thing : have a solid team built , but make every new build downloadable by everyone . Don't keep it private . If people want to flash them on their own and try to help , why shouldn't they? Maybe they'll run into some stuff in the logcat that the main team won't see
Last edited:
Filled in my details in spreadsheet.
---------- Post added at 12:58 PM ---------- Previous post was at 12:55 PM ----------
But a quick tutorial on how to just build a ROM would be nice for everyone who wants to help I think.
---------- Post added at 01:10 PM ---------- Previous post was at 12:58 PM ----------
Here you can find the details of my laptop which I will use for compiling:
http://www.amazon.de/Samsung-540U3C...9&sr=8-1&keywords=samsung+serie+5+ultra+touch
And one other thing: Will you create a new github repo for our project or will we still use atis112 repo?
---------- Post added at 12:58 PM ---------- Previous post was at 12:55 PM ----------
But a quick tutorial on how to just build a ROM would be nice for everyone who wants to help I think.
---------- Post added at 01:10 PM ---------- Previous post was at 12:58 PM ----------
Here you can find the details of my laptop which I will use for compiling:
http://www.amazon.de/Samsung-540U3C...9&sr=8-1&keywords=samsung+serie+5+ultra+touch
And one other thing: Will you create a new github repo for our project or will we still use atis112 repo?
Not everyone can use IRC, or Facebook, or WhatsApp. Maybe try to use some freeware web-applications for developers (with bug tracking included)? Something like Launchpad or GNU Savannah
How about a group chat on whatsapp?
Sent from my HTC Desire X using xda app-developers app
It cant record our conversationsI suggest to use an IRC channel.
Btw I don't have much time so I can't help
xpirt
Not all people are so social..
But I can be logged in to IRC 24\7 and log all the conversations and upload it from time to time. Or you can manually add bot to log our conversations
Last edited:
I have no dev experience, unfortunately, but I have a reasonably beasty pc and internet connection (31.4 / 2 mbps), linux experience and I'm competant with adb and fastboot.
I work freelance as a graphic designer, so between jobs I have loads of time. At the moment, I have loads of time...
...and of course, graphic work is a speciality. If anyone needs anything, just PM me.
I work freelance as a graphic designer, so between jobs I have loads of time. At the moment, I have loads of time...
...and of course, graphic work is a speciality. If anyone needs anything, just PM me.
Attachments
yep that seems fine.. just show us how it works and give us the procedures
Similar threads
- Locked
Top Liked Posts
-
There are no posts matching your filters.
-
36We, as a whole, have taken an initiative to create a team of developers who will focus on AOSP branch of development for this forum. The team is open to everybody.
Want to join us? Fill in your details in the spreadsheet and just inform us by posting in the thread.
Here's the Spreadsheet
Want to keep track of our progress or want to give us any suggestions? Here's our IRC channel and you can also see our chat history in case you missed anything.
PLEASE DON'T JOIN OUR IRC IF ITS NOT RELATED TO CM DEVELOPMENT!
Logs from channel: http://m.nyan.pl/xda/
Statistics (for fun): http://m.nyan.pl/irc/stats/protou.html
We are currently working on CM10.2 and the source codes are taken from arm6 org.
Find our sources here:
Device tree
Vendor tree
Common files
Kernel sources
Generic sources
Stable ROMs
CM10 (4.1.2) from @fozzy_fozzy: https://docs.google.com/file/d/0B2xUDHdk_M6HOUVkSDZJbWpqd3c/edit
Bugs: Bluetooth
Test ROMs (flash at your own risk!)
CM10.1 (4.2.2): https://drive.google.com/file/d/0B6lHfIKE8XmEd3phRVhJYkliQTQ/view?usp=sharing
Mirror for everything (thanks @mefistoreyon): https://cloud.mail.ru/public/559bfaa56b60/ROMS
All hail to @fozzy_fozzy for the latest releases
Bugs:
/Face recognition (Gallery FC)
/Battery drain
/App2SD (moving apps to SD card is impossible for now, no workaround)
/Overclocking (10.2, only placebo effect)
/Graphical glitches (Google Maps, etc)
/No sound when incoming notification (confirmed by two users)
/USB tethering (10.2), USB storage (10.1)
/Broken LED (when message received, red LED flashes over green)
/Handsfree during call not working (10.2)
Don't report bugs that were already reported
Other things works great.19No like I said, I have not push anything to github last months, allthough devicetree there is very similar to which one i worked on home, last two months, nearly every day... most important thing ,is like atis112 said before, a matching ramdisk... I have made a new which interacts with cm init.rc and boots up every compiled build i try in last weeks... Even Kitkat boots up & is far ok for building, already to do are minor fixes... Iḿ very sure, that in next weeks, we have/could same developments like HTC Pico.
---------- Post added at 05:25 PM ---------- Previous post was at 05:24 PM ----------
By the way, how could i get a thank Button?19Summary
ROMs
CM10
http://d-h.st/aUl
Everything for CM10
http://xdaforums.com/showpost.php?p=51935990&postcount=940
CM10.1
http://xdaforums.com/showpost.php?p=52606728&postcount=1133
Fixes (CM10.1)
Fixed storage names
http://xdaforums.com/showpost.php?p=52680352&postcount=1227
Fix for menu button issue
http://xdaforums.com/showpost.php?p=52629254&postcount=1177
Other
Datasheet with bugs
https://docs.google.com/spreadsheets/d/1Dnj3cFbf0GPebhjv6UcYqMkRfAgjsbOXWUXKZoGOoNI/edit#gid=0
Hit thanks for God's sake'18Good News Guys We have successfully booted CyanogenMod 11 on Desire X although there are many things Broken but they will be fixed by time we are currently fixing some major bugs so Stay tuned
Cheers,
Arslan15Cm10.2 & cm11
Have a booting & working CM10.2 (4.31) compiled ready. SD & EMMC work, also BT & today Ih hope fixing Wifi. Also I try to provide first Kitkat Rom tonight....
By the way. New Ramdisk with CM.Init and new updated init.target.rc...
Compiled with 3.4 Kernel
