Database Users

Devs, Please don't hide your Known Issues

I really don't want this to come across wrong, but I just have to say it.
Developers, I appreciate all your hard work. I understand this is all beta/test/etc. I understand it is free of cost, even to those who did donate to one dev or another. You do it because you want to, not because you have to.
But please, for the love of all that's good - keep an updated list of Known Issues!
It sucks having to read 50 pages of posts to try to figure out if a particular release is reliable or not, to find out if there's a key feature broken or buggy. What makes it worse is you can't tell when reading these threads which users are on which release, because many still post issues after they've been resolved. Others post things that aren't really "issues" but user error.
You know what your issues are, you read the threads and you fix the issues. But trying to find a decent rom to flash is very, very difficult when your OP says "No known problems" and the thread that follows show that to be very untrue. It generates a lot of extra posts with people posting things you already know about, and it generates a lot of bad will when someone flashes something only to find that there are a number of game breaking issues.
All it takes is to update a post, say #2, in your thread, with KNOWN ISSUES. Once you confirm a bug, whether you intend to fix it on your next release or not, add it to that thread. It helps you, as a dev keep track of the bug, and it helps potential downloaders know what bugs have been confirmed and make an educated decision as to whether they want to install your release.
Hiding known issues is something I don't think anyone does intentionally, but it feels that way sometimes. It feels like devs are in a popularity contest, and any admission of flaws in their particular ROM is a weakness. Well, to tell the truth, I and many others are sick of installing something that was CLAIMED to be working perfectly, only to have glaring problems that have been there for many versions.
For a civil and productive development community. Please. Be honest with your known issues. It will go a long way in building trust with the people who you're providing ROMs to, and will mean fewer posts for YOU to wade through of users reporting known issues, without having read 500 posts first.

I have a hard time believing that most devs actively hide them. Most of the time it's probably just a bit of laziness. But, yes, it would be helpful when comparing roms if the descriptions had a well-maintained list of active bugs.

Since the developers here are NOT getting paid (NO your $20 donation is not sh*t for the time it takes to make one of these roms), yes WE will have to bear the brunt of testing these roms out and letting them know what bugs if any are in them
The other issue is the people flashing these roms, coming from Eugene's to Whiskey to the ASOP roms may generate some ghosts in the software that the developers cannot duplicate themselves. I know that when I went with the TW 2.2 roms I had plenty of issues, more issues than I have had even when I was stock. Odining back to stock and reflashing the 4.2 TW fixed ALL my problems. Dont know what caused it but since I have flashed a couple of roms prior to that (no problems), I will assume there were some ghosts in my system. This is an example that unless a TW team member is holding MY phone and working on it, they may not be able to duplicate

They don't care to list them. It's beneath some of them.

Maybe AirBus should list "midair exploding engines" as a known issue too...
kponti said:
Since the developers here are NOT getting paid (NO your $20 donation is not sh*t for the time it takes to make one of these roms), yes WE will have to bear the brunt of testing these roms out and letting them know what bugs if any are in them
Click to expand...
Click to collapse
+1. Hell, at work I run a $100,000.00+ software suite and even that company won't do what the OP suggests!

If you have a problem with them stop using their roms go back to stock and see how much better theirs is even with a few bugs, not one of you has any right to complain. They do damn good work for free with some donations that do not come close to what they should be paid for it but they do not whine at all.

The problem I find is the "spammy" and useless comments average and pretentious users make which is both hard for the developer and the end user to read the threads. A dev releases a ROM and there is a guaranteed "Oh I can't wait to flash this" comment that will pop up. And there are some issues that are minor and are sometimes not related to the release that are posted and some pretentious loser who extends his ego by trying to make simple matters complicated. This forum didn't much of this problem before and I could quickly flash ROMs easily since I could clearly grasp the status on the ROM project.

I wish they would start a new thread with new releases. It's a pain to try to read through a 500 page thread, and you comments about this or that, and you have no idea which version the person is talking about. I gave up on custom roms and just using the leaked tmo 2.2, thanks for that Eugene

kponti said:
Since the developers here are NOT getting paid (NO your $20 donation is not sh*t for the time it takes to make one of these roms), yes WE will have to bear the brunt of testing these roms out and letting them know what bugs if any are in them
The other issue is the people flashing these roms, coming from Eugene's to Whiskey to the ASOP roms may generate some ghosts in the software that the developers cannot duplicate themselves. I know that when I went with the TW 2.2 roms I had plenty of issues, more issues than I have had even when I was stock. Odining back to stock and reflashing the 4.2 TW fixed ALL my problems. Dont know what caused it but since I have flashed a couple of roms prior to that (no problems), I will assume there were some ghosts in my system. This is an example that unless a TW team member is holding MY phone and working on it, they may not be able to duplicate
Click to expand...
Click to collapse
A $20 donation is not worth the risk of bricking a $550 phone just because they got "lazy" and didn't notify donators/downloaders of [a] potentially show-stopping issue.

Posted a new Thread in Dev section for the purpose of reporting issues. So if you have an issue please shoot it to me and I will post it in that thread.
Update: Here is the link for the WIKI page.
http://forum.xda-developers.com/wiki/index.php?title=Samsung_Galaxy_S_SGH-T959#ROMs

swehes said:
Posted a new Thread in Dev section for the purpose of reporting issues. So if you have an issue please shoot it to me and I will post it in that thread.
Click to expand...
Click to collapse
You are in a heap of trouble, a lot of people don't read, and you are gonna get 1000000000000000000000000000000000000000000000 repeats of the same issue.
"OMG! MY SD CAR DONES"T MOUNT< HELP ME!11!!111"

chui101 said:
I have a hard time believing that most devs actively hide them. Most of the time it's probably just a bit of laziness. But, yes, it would be helpful when comparing roms if the descriptions had a well-maintained list of active bugs.
Click to expand...
Click to collapse
The issue here is really that a forum is not the ideal place to manage software releases. A list of bugs emerges from community testing, but there's nowhere to "post" that list of issues, or attach it to a specific release. Since there's no way for the community to add such documentation, it falls on the ROM builder, who probably has other priorities.
This kind of project could be well served by using a real software project management software solution, such as say google code, which has an issue tracker and other useful features. But XDA does already give us a better tool than the forum - the XDA wiki!
I wish people would use the XDA wiki more extensively. This would be a good place to keep updated documentation such as this, without requiring the OP to keep a forum post updated with the latest findings. All the OP needs to do is link to the wiki page, and other people can help maintain it.

OK. Looking into Google Code.
(Update) So looking into the Google Code. What Licensing agreement are the ROMs under? Is it GPL v2 or v3 or another license?

swehes said:
OK. Looking into Google Code.
(Update) So looking into the Google Code. What Licensing agreement are the ROMs under? Is it GPL v2 or v3 or another license?
Click to expand...
Click to collapse
Depends on the project. The Linux kernel is GPLv2, so any kernels fall under that license. AOSP as a whole uses both GPL and apache code.
The issue with ROMs is that unless they're AOSP derived (like cyanogenmod) they often include binaries for which the license situation is murky at best, so google code isn't really an ideal fit for a "ROM" that's only ever released as a binary.
Really I was throwing google code out there as a well known example, there are tons of other ways to track issues. There are dedicated issue tracking systems such as trac, bugzilla, etc, but they require hosting. Most of the freely available hosted services require that you're running an open source project, which isn't necessarily true for the ROMs here.
IMO a serious project could very well benefit from such tools, but just using an XDA wiki page which community members can freely update is a great first step.

So looked into the Wiki for the Vibrant and have updated some information. Let me know what you guys think. Is this the way to go?
http://forum.xda-developers.com/wiki/index.php?title=Samsung_Galaxy_S_SGH-T959#ROMs

swehes said:
So looked into the Wiki for the Vibrant and have updated some information. Let me know what you guys think. Is this the way to go?
http://forum.xda-developers.com/wiki/index.php?title=Samsung_Galaxy_S_SGH-T959#ROMs
Click to expand...
Click to collapse
Not to be the "Spelling Nazi", and I am not even sure if you can change it, but it is "Kernel" not "Kernal". Also, the Dev on Team Whiskey is Sombionix, not Symbionix.
Otherwise, that looks like a great idea, and possible way of tracking things!
EDIT - I guess I could go ahead and make those tweaks, with it being a wiki and all couldn't I....
EDIT EDIT - Fixed it.

Stargazer3777 said:
Not to be the "Spelling Nazi", and I am not even sure if you can change it, but it is "Kernel" not "Kernal". Also, the Dev on Team Whiskey is Sombionix, not Symbionix.
Otherwise, that looks like a great idea, and possible way of tracking things!
EDIT - I guess I could go ahead and make those tweaks, with it being a wiki and all couldn't I....
EDIT EDIT - Fixed it.
Click to expand...
Click to collapse
Thanks. On both accounts.

Maybe this should be a post to Microsoft
To quote "there are known, unknowns and unknown, knowns and and even sometimes unknown,unknowns............but.........
Developers ----develop they do not become a bookkeeper of their development.........that is coordinating work...........good luck getting any developer in ANY Specialty to do that............. reporting bugs........
---Maybe this should be a post to Microsoft---

N8ter said:
A $20 donation is not worth the risk of bricking a $550 phone just because they got "lazy" and didn't notify donators/downloaders of [a] potentially show-stopping issue.
Click to expand...
Click to collapse
I have yet to see a REAL (completely dead) "bricked" vibrant from flashing a released Rom alone. I have seen a lot of user error cause boot loops or "soft-bricks" & HWL phones become unflashable because the end user didn't take the time to research though. As far as devs being "lazy" I dont really see that when the developer is coming here for us to tell him what else we find wrong. They are coding, you flash, you report back with a logcat. This is how development is made to my understanding. If ppl are to lazy to JUST do this then why shouldn't the developer discount long winded post or something they are not experiencing? If they know there is a bug its in the OP.
If you guys can change the interwebz & how 500 post per update are made completely useless please feel free to do so....

swehes said:
So looked into the Wiki for the Vibrant and have updated some information. Let me know what you guys think. Is this the way to go?
http://forum.xda-developers.com/wiki/index.php?title=Samsung_Galaxy_S_SGH-T959#ROMs
Click to expand...
Click to collapse
I think it's a pretty awesome start for sure
As a matter of personal taste, I think having an individual wiki page per ROM (with the known issues and other detailed info) might be nice, although I'm not sure what the policy on new pages is with the XDA wiki.
Speaking from professional experience, the most challenging aspect of any documentation system is always convincing people to use it. It's great to compile the information, but unless ROM builders and devs post a link to the wiki in the forum threads nobody will ever see it. Having good, community based documentation is a benefit to everybody though, so hopefully people will recognize the utility of it and encourage its growth!

Sick of zip developers (rant)

Typical scenario is;
v 0.1 based on this and that.
v 0.2 changed launcher, added ringtones
v 0.3 new wallpapers, added ram script
v 0.4 added new market, added google+
Excuse me!?! This is not development. This is stealing!
I think these people should just wank instead of copy/pasting. Would be more beneficial for both public and themselves.
Rant over.
Thank you.

calyxim said:
Typical scenario is;
v 0.1 based on this and that.
v 0.2 changed launcher, added ringtones
v 0.3 new wallpapers, added ram script
v 0.4 added new market, added google+
Excuse me!?! This is not development. This is stealing!
I think these people should just wank instead of copy/pasting. Would be more beneficial for both public and themselves.
Rant over.
Thank you.
Click to expand...
Click to collapse
Agreed, but if credit is given to original devs you can't really call it "stealing" cause Android is OSP after all...I'm no dev myself but it does seem many ROMs available are CM tweaks achievable with a few market downloads or simply AOSP with extra's...however sometimes certain ROMs begin as "Zip developments" and get later support with real devs and change fundamental features (kernels, code-base etc.) so it's not all bad...

Totally agree..........
But it's not the actual non-development of new roms that is getting on my nerves the most, its the constant *****ing and arguing through lack of understanding different languages etc etc..........
All i have to say is read the threads carefully as i've noticed some people who don't speak english very well get the hump on as they don't understand clearly what people are saying.
I know i've had my rants in some of these threads before and i don't blame anyone else for doing it too. I've managed to restrain myself the last few weeks as our arguments are falling on deaf ears so whats the point, i'll just ignore the idiots making fools out of themselves by bringing us stuff we've already had for a long time and stick to what i know best.

What you've said is true Scratch...even if the ROM cookers do bring something new often nobody knows what that new stuff is because of the poor English. I'm not trying to insult them but I would recommend, especially with a specialized thing such as compiling/ making a ROM, the English needs to be clear and concise so everyone knows what is being released, what changes have been made and what's been modified. More often than not, as you say Scratch, people get upset because of a misunderstanding. Maybe those struggling with the language can consult friends/devs and ask exactly how to express something they've done in their ROM so everybody is clear on what's happening.

Scratch0805 said:
...I've managed to restrain myself the last few weeks...
Click to expand...
Click to collapse
True, I have got quite a lot to say over this entire fiasco over the Android 4.0 "ports" and "source builds" that is currently playing out in the dev zone like a long dragging soap opera, but, its just not worth it, so, just let them argue over themselves who is first and who is the true dev and what not. Besides, it's not a good feeling when these Zip Devs accuse you of various stuffs when you speak out against them. It's extremely childish and irritating to read those posts, but I guess it can't be helped. Zip developers are not a localized phenomenon, they are everywhere, and since Android and ROMs like Cyanogenmod are Open Source, we have nothing to say, and have to live with it.
There's another new phenomenon which is playing out and can be seen on pretty much every ROM. Someone gets a ROM to boot / work at a basic level, create a thread and build up major hype and hoopla on it, and EVERYONE of these "devs" proclaim "I need help to do this and do that./..... bla bla bla". Zip dev is not such a big issue per se, but, the level of intellect is terribly low among the "devs". I believe most of them are what? 12-13 year olds, and, they act their age perfectly, unlike someone like Jacob.
/End Rant

Case in point, after Arco has announced his intentions and the fact he already has a working port in progress:
I was first, it was my idea, I continue and basta.
Click to expand...
Click to collapse
Enough said.

Ahah, doing small things for the buzz (pun intended), acquiring a fame in trolland

Lol, I've made myself clear on this too.
" the ability to read is good,
the ability to understand what you've read is great "

http://www.androidpolice.com/2011/1...om-developers-i-think-we-need-to-have-a-talk/

3xeno said:
dragging soap opera.
Click to expand...
Click to collapse
Don't you mean aosp opera? Hehe...okay, I'll stop with the bad jokes.
And I fully agree with the topic. Anyone can open up any rom .zip paste in some apps, reflash and repackage it as your own.

Agree with this. Sadly I'm one of the offenders, that will have a moan at people developing zip-roms. I accept that this isnt the greatest way to deal with people on forums like theese. But it seems the only good way to get my point across to people that aren't that great at english.
Although, I must add one thing. I've seen roms get tossed around the development forums like mad. It seems to go like this in the dev. forums.
People create a booting rom. Or compile a new one.
People add a few fixes, someone creates a spin off.
Original dev discontinues rom, other 'developers' ask to continue it, even when they have projects in hand.
Someone picks up the pieces months later. After even the re-contiuned rom is given up with.
People spin roms off from there.

All i can say is dear god. I have been reading all that threads last few days and i was frapped how people are shalow in glorifying them selves and their so called development skills. I didnt want to coment anything cauze i have run into such argument once before with someone who was constantly refusing to understand what i am saying and i dont want to do it again, so i leave my thoughts here.
So people should get on the ground for change and start doing something usefull instead of make dozen threads, first when you dig something, than another one when you are asking if it can be done and finaly one when you "do" something. What they have done is nothing. They are just thanks chasers. In last few days there were more new roms than it was for whole Wildfire lifetime.
I remember tje days when there was just three or four roms and they worked, you hear me, they worked. So stop posting such s**t unles u did something that is realy worth it.
Sent from my HTC Wildfire using xda premium

Yes you are right, zip development is horrible. Lately there has been a major rise in "new" roms that have been hitting the development thread. I swear I have seen at least 5 to 10 roms all based on CM7 or oxygen. And what's different? It's "fast and stable" "Is themed to look like ICS" "Has a script that I actually don't know what it does but it must do something good". And its "my" rom because I grabbed a rom.zip from a device that runs oxygen smoothly and added the boot.img and the build prop right from the CM7 rom.zip and then cooked it and I posted it under MY account so its MY rom. There is a problem though, my genius copy/paste skills on my computer that took forever to build up are limited to actually being able to fix problems with things like Bluetooth and GPS, etc. So what do I do then? Hell I request "help" to fix the problems and once a genius like acro or another real dev comes in and fixes it for me, I take the fix and say it was all MY work. AOSP stands for ANDROID OPEN SOURCE PROJECT. The source is open to anyone that can use linux terminal (that's half the problem). The other problem is that no one could be bothered taking the time to actually learn a skill. They want to do something now, and now only. They won't spend hours and days learning how to program in java or C because it takes "too long" and just wants to begin this so called "deving" now. This is a rant about zip development, but wait you say, I do .zip development though? Yes I do, but what I am talking about is .zip development that is based on a .zip that is actually OPEN SOURCE. If something is OPEN SOURCE there is no point in taking a compiled .zip and "porting it" to our device. You do this because its easy for you to hit download and copy and paste, but you don't "have the time" to setup a download of the source and compile it to a rom. Zip development that is for CLOSED SOURCE on the other hand is way different. HTC, MIUI, etc. are all roms that have no open source code so all the work has to be done based on a .zip. Since the code is not available this is the only option. This in my opinion is the only kind of good .zip development since there is no source to build from. I would love to download the source and mess around with the ICS source and try to compile something but my computer is got really bad specs and my internet is so slow. I will just leave that kind of work to acro and the real devs

I agree with this. Looking through the more recent Wildfire ROMS, I can see a pattern for most. So, I have started to come up with a fight back, for individuality and mostly, for a better mobile experience. It would mean a lot if you could help me out with THIS.
Sorry to ask in this thread, but I thought it might be a good idea

Before I get accused of zipfile developing, I only compiled an edited kernel for the ROM to allow touchscreen to work a little.
I am not a "zipfile" developer and I am not going to be, my interest is in kernels.
I happened to come to xda at the wrong time, first thing kaassaus did was ask me to follow a tutorial to get touchscreen working (which took all of 20 seconds).
I think posting an ICS zip is okay FOR NOW because there is no OPEN source for the wildfire for it, and Arco is NOT breaking the GPL because he hasn't redistributed it yet.
Sent from my HTC Wildfire

We are not accusing anyone. My point is dev section is not a learning section. Those who want to learn development can pop into chefs section instead of releasing a rom with 2 zillion bugs.
There is a reason for this forum is not called xda-tweakers. Because our devs are devs. They are not steve jobs like tweakers.
2nd rant over. Class dismissed

Okay, Zip development is not so bad, actualy is needed in some points. For flashing kernels or some other things. But look at some of that AOSP-fast and stable roms. What do they bring us? Nothing. It is just repacked CM nightly or stable. To "develop" such rom you need WinZip and in best case Android SDK if they decide to decompile and recompile few apps instead of treating them with winzip too to change few icons and voila, NEW ROM. Better yet someome will take any theme and implement it into framework.And he will be so proud because his rom has diferent look. What else we can still expect is ES file explorer instead of OI, Miui galery, themed keyborad, different font and unforgetable scripts which do god knows what. They are the main part. Is that a rom? No it isn't my dear friends. Its a disrespect to any real developer here. All that we already have. We have themes, we have scripts we have everything that flashable and we dont need another yet ****y rom to tell us what is fast and stable.
Sent from my HTC Wildfire using xda premium

I don't find anything wrong in updating an already present ROM's with new applications update ,... even though i must say there is a trend in past few weeks that lot of ROM's in buzz section were merely identical and there was no development in them

I was browsing the old threads of the Dev Zone, and came on this:
http://forum.xda-developers.com/showthread.php?t=884659
Amazing, right? It's deja vu all over again.. (PS - Don't bump that please. lol)

I am a noob, and I know I will never be as experienced as other developers.
That is why I do not develop ROMs, and develop things I am good at.

[DEV] Finding a devs team

Hey guys and girlz,
as many of you know, the developement for our device is not that great and fast because everybody (except from ivendor and arco and maybe some others) is working alone on a ROM/kernel. We could speed this up by building a dev team where all devs for our device and maybe from galaxy w can work together and improve ROM for ROM instead of doing each ROM alone.
Hope we can do this :good:
If anybody is interested, post it here or PM me
Greets and regards,
markey

AW: [DEV] Finding a devs team
markey97 said:
Hey guys and girlz,
as many of you know, the developement for our device is not that great and fast because everybody (except from ivendor and arco and maybe some others) is working alone on a ROM/kernel. We could speed this up by building a dev team where all devs for our device and maybe from galaxy w can work together and improve ROM for ROM instead of doing each ROM alone.
Hope we can do this :good:
If anybody is interested, post it here or PM me
Greets and regards,
markey
Click to expand...
Click to collapse
Hm. Mate are you blind? Look at this forum. We have a lot of roms, some are even twice there from 2 different developers.
For me, personally its perfect like it is. Arco and Ivendor as lead developers for CM10. Other devs can contribute or take their work and make a new rom out of it.
Especially for a almost 2 years old device our forum is really awesome and you should be happy for what weve got here.
Just my 2 cents.
P.s: This is the development section. You should ask things like that on the General section, in the i9001 thread.
Sent from my GT-I9001 using xda app-developers app

XeLLaR* said:
Hm. Mate are you blind? Look at this forum. We have a lot of roms, some are even twice there from 2 different developers.
For me, personally its perfect like it is. Arco and Ivendor as lead developers for CM10. Other devs can contribute or take their work and make a new rom out of it.
Especially for a almost 2 years old device our forum is really awesome and you should be happy for what weve got here.
Just my 2 cents.
P.s: This is the development section. You should ask things like that on the General section, in the i9001 thread.
Sent from my GT-I9001 using xda app-developers app
Click to expand...
Click to collapse
First of all, i appreciate all the work of ivendor , skywalker, brood, xistance and arco and others who did an amazing job of porting major roms to our device. But i must honestly say, i agree on some points with the OP. It is amazing with what we achieved on our small but awesome community, but our phone is getting old and eventually we will be left behind. So now it is the best time to combine all of the knowledge that is hidden in our i9001 section to ensure the future.
In the past year i have been in this section i saw a lot of stuff that could be fixed faster if people would communicate more, like the well known cm9 camera problem (i dont know for sure there was miscommunication as i dont know what happened in the background). A dev team would be awesome.
But i am afraid that this won't work anymore. The glorious days of the i9001 are over. Many good devs left us.
But is is worth the shot. Would be so awesome! If you have any android knowledge, please join.
(I am to stupid. I cant join. I know how qtADB works but that is all).
Also i like the idea of combining the two devices and make a giant dev team for both so we can benefit from there knowledge and they from ours!
Verstuurd van mijn GT-I9001 met Tapatalk

XeLLaR* said:
Hm. Mate are you blind? Look at this forum. We have a lot of roms, some are even twice there from 2 different developers.
For me, personally its perfect like it is. Arco and Ivendor as lead developers for CM10. Other devs can contribute or take their work and make a new rom out of it.
Especially for a almost 2 years old device our forum is really awesome and you should be happy for what weve got here.
Just my 2 cents.
P.s: This is the development section. You should ask things like that on the General section, in the i9001 thread.
Sent from my GT-I9001 using xda app-developers app
Click to expand...
Click to collapse
No i'm not, otherwise I couldn't have read the forum and written this here
(Just joking)
I know that we have a lot of ROMs, but there are some from 2 different developers because one of them hasn't updated very long or stopped the project and then a new dev took the work.
Thats your personal opinion and I accept it.
I mean this all because of the bugs that have to be fixed.
No its not that awesome, look at the dhd, they have a big dev team who solves most of the bugs there and they have fully functional Android 4.2 and MANY more ROMs than we have also have a look at some other 2 or more year old devices, most of them have big dev teams who do fast and great work.
I really appreciate the work of all our developers (!!we have a 3.4 kernel which even much newer and better devices don't have!!) but we can make this even better and faster.
Thanks i know this but in general section we couldn't get a team together and i also forgot about this section because i mostly (nearly only) use the developement section
Greets and regards,
markey

I seem to agree with xellar's view. Our I9001 forum is great as it is for a two year old device and development seems to be moving forward at a well-placed pace. I dont see any point in creating a ''dev team'' . Dont get me wrong , I'd love to see it happen. But Im comfortable with the pace here .

AW: [DEV] Finding a devs team
I would also apreciate a dev. BUT the developement of the last 2 years was that good, that i can't comlpain on anything. It works very well the way it goes now. Maybe in the near future (~6 moths) when more importent (doesn't mean the other are unimportant) devs leave the s+ and 5.0 will be roll out, maybe then we need a dev-team.
But we have already s.t. like dev-teams:
Arco and Ivendor (CM9/10)
The kernel devs (Erik, castagna, Biagio, Christopher, ...)
Xistance and Doom (CM10.1)
They all share allready there knowledge and function.
So... No need to hurry in my opinion :beer:
"...nothing is more powerful than a young boy's wish. Except an Apache helicopter..." -Ted

i think we have a lack of devs contributing to really port the newer versions of android. its only arco and ivendor who are doing this and since arco wanted to concentrate more on his own device its only ivendor (arco is yet still involved with our phone). everyone else is "just" forking from ivendor, aokp, aosp and paranoid which is great and which is not necessarily easy. without them there would be nothing else but the cm rom. still its not comparable to ivendors or arcos work. i dont want to diminish the importance of the work of others (sadly i have to always mention it when saying things like that...). i just didn't see them commit to ivendors github and ivendors credits concede my point.

AW: [DEV] Finding a devs team
I'd love to be in the team
Sent from my GT-I9001 using xda app-developers app

dr.wtf said:
i think we have a lack of devs contributing to really port the newer versions of android. its only arco and ivendor who are doing this and since arco wanted to concentrate more on his own device its only ivendor (arco is yet still involved with our phone). everyone else is "just" forking from ivendor, aokp, aosp and paranoid which is great and which is not necessarily easy. without them there would be nothing else but the cm rom. still its not comparable to ivendors or arcos work. i dont want to diminish the importance of the work of others (sadly i have to always mention it when saying things like that...). i just didn't see them commit to ivendors github and ivendors credits concede my point.
Click to expand...
Click to collapse
As true as this is, I still don't like the fact that you say we just fork their work. Both arco and ivendor haven't even started doing any real work on 4.2, forget giving us anything. Camcory and I have brought 4.2 by ourselves, just using arco's kernel source(which is REALLY important so I'm saying nothing to arco).

you probably saw what a mess the "perfectly working cm7" was even though mazen said hes not a real developer. when the 3.4 kernel came up it turned out to be not properly ported. no offense to both of those guys since cm7 actually was usable and the kernel had its right to exist (educk, if you read this, no need to defend yourself, i've read the whole thread).
but you must understand that im kind of suspicious with new things since i don't know if you know what youre doing. im not judging, i really don't know because i'm not qualified. also i dont see anything else going on on your github but your 4.2 porting. so i cant see any references. i also dont see any commits from camcory. thats another thing i cant get an opinion about.
but arco and ivendor have proven to be pretty skilled. i remember someone saying we would never have a 3.x kernel because someone who wanted to port it would be insane...
im still thankful for what youre doing since if ivendor quits its all on you
and im sorry you got in the "just forking" cathegory and everybody else who doesn't feel he belongs there. im just generalizing...
just actually saw your sig. still doesn't change much

dr.wtf said:
you probably saw what a mess the "perfectly working cm7" was even though mazen said hes not a real developer. when the 3.4 kernel came up it turned out to be not properly ported. no offense to both of those guys since cm7 actually was usable and the kernel had its right to exist (educk, if you read this, no need to defend yourself, i've read the whole thread).
but you must understand that im kind of suspicious with new things since i don't know if you know what youre doing. im not judging, i really don't know because i'm not qualified. also i dont see anything else going on on your github but your 4.2 porting. so i cant see any references. i also dont see any commits from camcory. thats another thing i cant get an opinion about.
but arco and ivendor have proven to be pretty skilled. i remember someone saying we would never have a 3.x kernel because someone who wanted to port it would be insane...
im still thankful for what youre doing since if ivendor quits its all on you
and im sorry you got in the "just forking" cathegory and everybody else who doesn't feel he belongs there. im just generalizing...
just actually saw your sig. still doesn't change much
Click to expand...
Click to collapse
Only one thing to say:: does not make any sense at all...
What op asked is on team..wats happening here is just nonsense..if somebody interested to work with him pls do it..if u are not interested get the f** k out of here...its not must that each and everyone has to put their point of view..if u are ready to help then help..otherwise leave from this thread...simple....
Sent from my GT-I9001 using xda app-developers app

AW: [DEV] Finding a devs team
This thread needs to be closed. Its like a slap in the face for all of our developers. Shame on you! Show some respect to them. They sacrifiy a lot time to give us a better user experience for our phones but well, everyone is like "hurrdhurr dat fone is not even like a galaxy s3 now brah after flasching tis rom my fone suks bad ass".. Instead of saying thanks to the developers or donate some buck to them for a fresh beer or something.
Always remember this is a single core device, with a midrange chipset and it cant handle even close as much as a S3 or S2.
We have a fully working (vsync and tripple buffer are working and all ither stuff) Jellybean cm10. Not even the s2 or s3 have this because of the lack of sources for their exynos cpus.
I hate this unrepectless behavior.
Be happy with what you got here FOR FREE. And for a Non-flagship device like our i9001, we have A HELL OF A LOT roms and kernels!
Get your **** together people.
Sent from my GT-I9001 using xda app-developers app

Disrespectfull: YES understandeble: YES.
At our forum/development we got 1-person teams. Some ROMS are made with someone on the background (CM9/CM10/CM10.1).. But the other ROMS that are based on these are made and maintained by 1 person.
I got the feeling that some of us dont have PATIENCE..
And that is something what is very stupid.
Teams are working faster and fixing faster and better bugs in ROMS, that is true.
If the OP want to make a team just ask some developers for godssake. These topic are as disrespectfull as saying WHEN ARE YOU GOING TO UPDATE OR FIXING THIS OR THAT in every goddamm topic.
Just my opnion..

dr.wtf said:
you probably saw what a mess the "perfectly working cm7" was even though mazen said hes not a real developer. when the 3.4 kernel came up it turned out to be not properly ported. no offense to both of those guys since cm7 actually was usable and the kernel had its right to exist (educk, if you read this, no need to defend yourself, i've read the whole thread).
but you must understand that im kind of suspicious with new things since i don't know if you know what youre doing. im not judging, i really don't know because i'm not qualified. also i dont see anything else going on on your github but your 4.2 porting. so i cant see any references. i also dont see any commits from camcory. thats another thing i cant get an opinion about.
but arco and ivendor have proven to be pretty skilled. i remember someone saying we would never have a 3.x kernel because someone who wanted to port it would be insane...
im still thankful for what youre doing since if ivendor quits its all on you
and im sorry you got in the "just forking" cathegory and everybody else who doesn't feel he belongs there. im just generalizing...
just actually saw your sig. still doesn't change much
Click to expand...
Click to collapse
Alright, even through, I shouldn't have any comments here as you already screw things up really bad, I feel like I must do it to clear things up a bit around here.
First of all, you said yourself that you don't have any knowledge related to software development, so why are you messing with people that actually devote time to do it? If you have no ideea what development is, why are you talking about it in this manner? I mean, it is ok to ask or to make mistakes, everybody does, nobody is perfect but I consider this post offensive and I must defend myself here.
Second, as far as I'm consern, my GitHub is MINE and I and only I will decide when to push something there. I cannot be forced by anyone to do anything. So, your sentece "I didn's see anything going on on your github" so what?!? Tell me, why should I post anything just for you to see it? Ah, you think I lack activity? Again, so what? I or any other Open Source developer cannot be forced by anyone to publish something. We do this because we like it, we are not paid for it. Maybe if you would pay me to do these things, yeah you could have the right to judge my activity. This is open source, this is Android, the developers are bringing stuff to the end user but the end user is free to choose if he wants to use that piece of software or if he doesn't want to use that software. Same applies to you, you don't have to flash anything on your phone just because it's there online, if you don't like it, don't use it .
About my 3.4 kernel. I mentioned in the OP of the thread that it is an early "alpha" nothing more. I even used the word "preview". If the end user doesn't like the way the kernel is, than he wont use it.
Oh, and I'm not supposed to say this but I'll take this opportunity just for you to see that I'm not lacking activity and actually I want to develop that 3.4 kernel, also I'll explain why I didn't update anything on github.
I worked locally, and everytime I fixed something, 2 other errors came up, after I fixed those 2, another 3 came up and so on. That's why I choosed not to push anything to git until I get something concret. I said this a million times actually: I have no ideea when that kernel will be ready and if it will be ready, I am going to decide if it will be published to git and XDA or not. This is my personal decision, you can't influence me in any way to do anything.
Also, I'm not a full time developer, I'm still a beginer, I'm still learning things here and I choosed to share my work with others, here on XDA because I thought that my work could be usefull. If you or anyone else don't find it usefull, as I said, don't use it .
Also, ivendor won't quit either and there is nothing on me...again, you are trying to push me...this is hilarious...I choosed to start the 3.4 kernel project but that doesn't mean that I must finish it... I really hope you understood something from this post, if not please, just let it go and ignore it. Also, there is no need to apologise, you were wrong by trying to put pressure on me but I ignored it, as you probaly noticed.
Cheers,
Erik

Topic reported.
Argument:
Insulting to our developers an absolutly not development related..
Cheers

Thread Closed:
This topic has turned to a flame war and no longer serves a purpose.
Appreciate the work the devs do, as they aren't required to do anything...
~ The-Captain

Galaxy Note 10.1 2014 Exynos Developer Device

Hello everyone,
most of you probably don't know me since I did not develop for Samsung devices for quite some time now.
I would be interested in aiding the Exynos 5420 development scene (in particular on the Galaxy Note 10.1) and prepare a custom Android distribution for it (Team EOS 5.0 - Lollipop).
I can get all the required drivers and binaries I need for development, since most of it is open source luckily.
And the Nexus 10 (manta) can still be used as reference for many things.
All I need is a development device to debug on.
It is particularly important that this is the Galaxy Note 10.1 EXYNOS (WiFi-only variant), and not the LTE (Qualcomm) variant.
I created this thread to ask whether someone has a spare device lying around, maybe because of the little development on Exynos 5 devices, or if people would be willing to donate a device (I'm a university student and unfortunately can not afford the full price for a new device. I'm willing to dive into the Exynos development scene and spend time on this device though, including extensive debugging).
You can leave a reply in this thread or contact me on gmail: [email protected]

I have a better idea. Sending device is a problem. But we can donate to you, and then u can purchase P600 or P601 on SWAPA or EBAY. not new but fully working
I would be glad to see working AOSP/MAHDI or other ROMs runnig on my P601

Yeah, that was the initial idea.
I would pay any shipping costs or parts of a device (a used one is perfectly fine).
The issue I see is that probably not enough people willing to donate enough small amounts of money, hence I asked if someone had a spare device I could buy or pay the shipping costs.

RaymanFX said:
Yeah, that was the initial idea.
I would pay any shipping costs or parts of a device (a used one is perfectly fine).
The issue I see is that probably not enough people willing to donate enough small amounts of money, hence I asked if someone had a spare device I could buy or pay the shipping costs.
Click to expand...
Click to collapse
I think it would be better to ask for donations because there is not a lot of people here although it would be hard. There have been previous instances where at least 2 different devs raised donations for this device before stopping development shortly after so people do have some trust issues. It would take a while but i'm sure people would donate considering you are offering an AOSP experience. If you renamed this thread to something like: Donations needed for new device- AOSP rom development. Then it would catch a lot of eyes because that's what a lot of people want The question remains whether people would actually donate. The average cost for you would be around 250-300 euros I think. That means you would need around 28 people (10 each). Whatever way you decide to go down, I wish you luck and I look forward to any rom developments if you do manage to get the device :good:

You seem to have quite a respectable history (in both Rom & kernel developement), so I think getting enough donations should be doable (and I'd be willing to donate a few bucks myself)
But I do have a few questions:
1) What about warranty? Some devs who had collected donations for a (used) device, have bricked their devices -> no more developement
Therefore P600 owners might be scared / hard to convince
2) what exactly is "Team EOS 5.0" and what makes it different from other Roms? Would you perhaps consider developing other Roms / kernels as well? (like porting over PA for example?)
Or would you maybe consider becoming the official P600 CyanogenMod maintainer (since we don't have one, yet)? [<- I think this one would be reason enough to donate]
Last but not least:
You could ask one of the XDA members who managed the previous donation-collections for help (they have successfully done it before, so they might be able to do it again :fingers-crossed: )
PS: The Note 10.1 2014 is great for college, trust me - I'm a student, too . All you need is the Papyrus-App from the Play Store.

Thank you two for your reasonable thoughts.
I think the main reason why the previous developers stopped developing for this device rather quickly is the Exynos chip.
The main difference between me and anyone else is (or so I believe) the fact that I am especially interested in developing for the Exynos 5420 chip and the drivers for it (mainly from the Insignal forum source).
As far as bricked devices, I can say I had a Samsung device before, and as long as the bootloader is unlockable and access to ODIN (The firmware flashing tool) is granted, a hard brick is rather hard to achieve. I see little risk here, and I assume my previous development experience will prevent me from making major mistakes in that regard.
A new device would cost me approximately 350€, so if we could collect about 300$ with donations (which would equal something like 270€), I'd pay the remaining costs.
People are of course free to check my development history and/or references first and see if they think I would benefit the aosp development scene for this device.
The ROM I mentioned (Team EOS 5.0 lollipop) is essentially AOSP 5.0 with selected features that we code ourselves, like EOS Weather, or the NX gesture interface.
If people however see the need for an official CM maintainer, I'd be happy to become this as well, all I need is a device to debug and develop on, I'd be willing to spend the time to officially maintain this device.
Other developers and/or contributors should also expect support from me in areas of kernel development or AOSP custom ROM development. I believe in 'sharing is caring', so all my knowledge and achievements on this device shall benefit the community.
If some of you could maybe contact the people who raised donations before, I'd be thankful and gratious for the support. All donations will be listed here and the whole process shall be as transparent as possible.

RaymanFX said:
Thank you two for your reasonable thoughts.
I think the main reason why the previous developers stopped developing for this device rather quickly is the Exynos chip.
The main difference between me and anyone else is (or so I believe) the fact that I am especially interested in developing for the Exynos 5420 chip and the drivers for it (mainly from the Insignal forum source).
As far as bricked devices, I can say I had a Samsung device before, and as long as the bootloader is unlockable and access to ODIN (The firmware flashing tool) is granted, a hard brick is rather hard to achieve. I see little risk here, and I assume my previous development experience will prevent me from making major mistakes in that regard.
A new device would cost me approximately 350€, so if we could collect about 300$ with donations (which would equal something like 270€), I'd pay the remaining costs.
People are of course free to check my development history and/or references first and see if they think I would benefit the aosp development scene for this device.
The ROM I mentioned (Team EOS 5.0 lollipop) is essentially AOSP 5.0 with selected features that we code ourselves, like EOS Weather, or the NX gesture interface.
If people however see the need for an official CM maintainer, I'd be happy to become this as well, all I need is a device to debug and develop on, I'd be willing to spend the time to officially maintain this device.
Other developers and/or contributors should also expect support from me in areas of kernel development or AOSP custom ROM development. I believe in 'sharing is caring', so all my knowledge and achievements on this device shall benefit the community.
If some of you could maybe contact the people who raised donations before, I'd be thankful and gratious for the support. All donations will be listed here and the whole process shall be as transparent as possible.
Click to expand...
Click to collapse
Hi. Here's the most recent donation thread which was successful :good:
http://forum.xda-developers.com/showthread.php?t=2742793
I don't see why another thread is needed though. I don't mind opening one up for you but you might as well use this one if you just rename it and state your intentions in the op.

22sl22 said:
Hi. Here's the most recent donation thread which was successful :good:
http://forum.xda-developers.com/showthread.php?t=2742793
I don't see why another thread is needed though. I don't mind opening one up for you but you might as well use this one if you just rename it and state your intentions in the op.
Click to expand...
Click to collapse
Okay, so if maybe one of you guys, with good contact to the community, could open a new donatiion thread to collect the ~300$, I'd be grateful.
Or maybe @drrasii could chime in here and edit his first donation thread and link here as a reference to let people know what I want to do.
As I said above, I'd be willing to become the official CM maintainer, or if CM refuses to accept this for some reason, I'd host the needed sources for the device on my personal GitHub and keep it updated so people can build whatever ROM they want.
Of course, the first goal would be to get Lollipop running on this tablet, which I'd start with as soon as the device is ordered/has arrived.

Hey guys. That donation thread I started a while ago was on a whim cause I wanted Hyperdrive by sbreen on my Note. Was lucky enough to have him commit and get enough people chipping in for the tablet which was met with success. I'm by no means a great organizer or somebody with tight connections here on XDA . Probably would be best if someone who wanted to head it up would start a new thread stating the case.
Best of luck!
RaymanFX said:
Okay, so if maybe one of you guys, with good contact to the community, could open a new donatiion thread to collect the ~300$, I'd be grateful.
Or maybe @drrasii could chime in here and edit his first donation thread and link here as a reference to let people know what I want to do.
As I said above, I'd be willing to become the official CM maintainer, or if CM refuses to accept this for some reason, I'd host the needed sources for the device on my personal GitHub and keep it updated so people can build whatever ROM they want.
Of course, the first goal would be to get Lollipop running on this tablet, which I'd start with as soon as the device is ordered/has arrived.
Click to expand...
Click to collapse

Thanks for the quick answer.
Could one of you guys (@22sl22 or @r4yN) then open a new donation thread and explain a bit about this thread and my plans?
If we manage to handle this process rather quickly, people should be able to enjoy L on this tablet soon hopefully.

RaymanFX said:
Thanks for the quick answer.
Could one of you guys (@22sl22 or @r4yN) then open a new donation thread and explain a bit about this thread and my plans?
If we manage to handle this process rather quickly, people should be able to enjoy L on this tablet soon hopefully.
Click to expand...
Click to collapse
Sure, i'll open one now :good:
I'll also post a message in here after the new thread has been created so that people know http://forum.xda-developers.com/galaxy-note-10-2014/general/rumours-plans-to-android-5-0-t2861225
EDIT: before I open the thread, how much do you actually need? $300 is about 240 Euros, not 270 so we will need a bit more, say $350, would that be OK?

Thank you very much.
Actually, 300$ (240$) is enough, I'd be willing to pay the other 100€ myself if it needs to be.
I want to get started rather quickly and have L running on this device, so I'd order the device as soon as the 300$ are collected.

Why a P600 model and not the P601 model?
The p601 to develop is exactly the same from p600 plus the phone side.
Sent from my SM-P601 using XDA Free mobile app

Why the delay? Here are the first 10 €!
RaymanFX said:
Thank you very much.
Actually, 300$ (240$) is enough, I'd be willing to pay the other 100€ myself if it needs to be.
I want to get started rather quickly and have L running on this device, so I'd order the device as soon as the 300$ are collected.
Click to expand...
Click to collapse
Hi RaymanFX!
Glad to see that a real dev wants to take our device and port CM11 for us.
I do not make many words, but simply push the first $ 12.12 to you.
That's the current rates for 10, -€.
Hope it works as good as for sbreen (dev from HyperdriveRom) and many people jumps like lemmings behind me. :good: Haha!
Hope also we get the money quickly together and will try to continue to encourage people to make a small donation.
10,-€
Transaktionscode:
7R473626855605042
You also get a short pm

Hey RaymanFX, excited for asop 5.0 but curious about some of the stock features that make this tablet. Is there any way to preserve multi window support or s-pen features ?

To all Cyanogenmod lovers out there

Hi,
I just thought it could be worth mentioning that there's a device request thread on Cyanogenmod forums for our beloved Idol 3 :
http://forum.cyanogenmod.org/topic/111850-alcatel-onetouch-idol-3-55/
May I suggest that everyone who wants a Cyanogen rom to be ported on our phones should take a minute to register there and add their voices to the request ?
There's already 24 posts in this thread

Already demanded it

Cool

Just made a post, but later found out that posting a request for CM does not guarantee anything. In the sticky it states
Now, what does this mean to you? First off, requesting anywhere in the CM forum, the CM Blog, or the Facebook/Google+/Twitter accounts for device XX to be supported is probably a waste of your time and anybody who reads said request. CyanogenMod does not work on device requests as there is no guaranteeing that a current CM maintainer is even interested in the device. Additionally, its not as simple as 'porting' code, the device trees must be coded from scratch and made to work with the AOSP sourced code and CM enhancements. This takes a large amount of time and effort, especially when the device's OEM fails to release the latest version of Android for it. Second, in hoping a worthy developer sees the post and decides to take up the project... well, that is probably just wishful thinking. Many developers do not like interacting with end users (too much finger pointing between both devs and users or anger directed at the devs for something working other than how the user expects - it happens far too often); because of that, many developers don't frequent the forum (or if they do, they only view the forums for the devices they maintain).
The best way to get a device official support is not requesting it from the CM team, but learning how to do it yourself or encouraging a maintainer of an unofficial build to submit their code for review. Many developers will work on unofficial ports on the xda-developers forum, so that would be the first place to check out. If there isn't any work currently being done, you can attempt it yourself. There is a pretty in-depth article in the wiki explaining a lot of the steps of porting a device (as the bottom of the wiki states, nothing can cover every single process of porting, but it is a really great start).
Click to expand...
Click to collapse
So it would need to be someone willing to take the time out to buy an Idol 3, if one has not done so already, and then port the code for our device out of their free time. And considering the userbase for this phone does not seem all that large to be noticed, I'm not sure if CM will work on our phones anytime soon.

Well thank you very much for your posts and your research.
I'm afraid you're right, but we had to ask
Let's not lose hope too soon anyway, the fact that the device request thread exist seems to be a good point. I don't know if any device had received a CM port because of this thread, but... why not ?
I've red that Alcatel and cyanogen had been in contact for a tablet. The project has been cancelled but this might suggest they could have access to resources that would ease their work (pilots ?).
Original rom on the idol is pretty much stock Android, this is a good thing too (well I'm not a developer but I guess it's easier when it's close to the original).
And, like you said, even if the user base is not that large, chances that someone from cyanogen got seduced by the idol (like we did) are still possible... (this is the moment where everybody crosses their fingers ).
Anyway thanks again !
The thread has now 31 posts (ah no, 32 webgaffeur just added his voice !)
Thanks to all the people that took some time to post there, let's not give it up : it's time to flood the forum !

i had posted the github with source for the phone but no one seems to respond not even one single admin? we can ask other devs crdroid pacrom dirty unicorns paranoid etc.

Alas, I think Brian is right : it's probably a waste of time posting on the device request thread
I checked devices with a lot more posts and views than ours and... nothing from a dev (like huyawei and Asus zenforce 5).
Asking to other rom devs will probably be useless also. Our only hope is that a competent developer buy an idol and start working on it... If this happens, I'm pretty sure he will share his work on XDA.
Well, meanwhile we already have root, twrp and xposed working, so I guess the best thing to do is to customise out phones till it suits our needs and that's all.
Let's hope also that Alcatel will continue to push updates (marshmallow ?)
Anyway thanks for your efforts Gecko.

Sorry, didn't mean to rain on anyones parade. Just wanted to let everyone know what the stickied thread on the CM forum for device requests stated. I'm not saying it won't ever happen, just that it might take some time to get a valued reputable dev who owns, or wouldn't mind purchasing the Idol 3 and working on it for us. Most dev's accept donations of devices that want development on from the users, so if we were able to locate and contact a reputable dev, asking them if we were to provide them with the device, would they mind porting or creating a ROM for it. It's worth a try. Maybe start a bounty or fundraiser etc. I myself do not know of any dev's that would be willing to work on this device as the ones I do know of have only worked on Samsung devices.

I don't know any dev at all
P.S. : thread has 34 answers now !

Cannadoux said:
I don't know any dev at all
P.S. : thread has 34 answers now !
Click to expand...
Click to collapse
theres always other devs like pacrom paranoid android crdroid and omnirom even dirtyy unicorns

Good news, it seems we haven't hoped for nothing : http://www.cyanogenmod.org/blog/releases-releases-releases-august-2015#comment-2229134454
Thanks to @purple.epod for posting the news.
From cirwl himself : "A couple of us have one, and kernel source was just released, so strong possibility of yes"
Yiiiihaaaa

this is great i hope that we get a nightly soon