can someone tell me why the developers have 2.3.4 rom in development, with bugs and little support ??? when it is better to devote time to a single good and seriously attended !!!!
Sent from my Redmi 3S using XDA-Developers Legacy app
Same question. There are a few devs who would work on one build then abandon the project completely, and make another build of a different ROM.
Because most of that So called Development is just copy paste job. those guys don't actually develop anything by themselves. otherwise they could have fixed it, instead they wait for actual developers to fix it and just copy from them. :silly:
kraatus90 said:
Because most of that So called Development is just copy paste job. those guys don't actually develop anything by themselves. otherwise they could have fixed it, instead they wait for actual developers to fix it and just copy from them. :silly:
Click to expand...
Click to collapse
agreed
[email protected] said:
can someone tell me why the developers have 2.3.4 rom in development, with bugs and little support ??? when it is better to devote time to a single good and seriously attended !!!!
Sent from my Redmi 3S using XDA-Developers Legacy app
Click to expand...
Click to collapse
kraatus90 said:
Because most of that So called Development is just copy paste job. those guys don't actually develop anything by themselves. otherwise they could have fixed it, instead they wait for actual developers to fix it and just copy from them. :silly:
Click to expand...
Click to collapse
1. You will know then answer when you try to compile one ROM (Not developing).
2. Compiling a ROM is not just a Copy & Paste work. If it's so... Do yourself.... (its just copy & paste nah..?)
So here is a answer. I'm also started Android Development just 2 weeks ago. And i compiled 4 different ROMs : Lineage, Candy, Slim, Glaze. I'm not doing it for you. But for me. I wanted to learn, no one can start from "Coding Everything from Scratch" especially legacy softwares like kernel and other things. So we start from compiling.... When we successfully compiled a ROM by facing and fixing many Errors. We move on to a new ROM, Coz New ROM will give new errors and we can learn to fix them. You may ask "Why you cant learn from Improving a rom...?" and my answer is "NO ONE IS GONNA TEACH ME HOW TO IMPROVE A ROM". Self learning needs lots of trial and error. So we building many ROMs. If you don't like that or you are a cry baby who cries for "XXXXX is not working" or "Poor XXXX". Just stick with STOCK ROM. XDA is for Learning and Not Only for SERVING YOU A BUG FREE, FULLY OPTIMIZED, FULLY FEATURED CUSTOM ROM for FREE.
Sorry.... if anything hurts anyone... I mean it.
dineshthangavel47 said:
1. You will know then answer when you try to compile one ROM (Not developing).
2. Compiling a ROM is not just a Copy & Paste work. If it's so... Do yourself.... (its just copy & paste nah..?)
So here is a answer. I'm also started Android Development just 2 weeks ago. And i compiled 4 different ROMs : Lineage, Candy, Slim, Glaze. I'm not doing it for you. But for me. I wanted to learn, no one can start from "Coding Everything from Scratch" especially legacy softwares like kernel and other things. So we start from compiling.... When we successfully compiled a ROM by facing and fixing many Errors. We move on to a new ROM, Coz New ROM will give new errors and we can learn to fix them. You may ask "Why you cant learn from Improving a rom...?" and my answer is "NO ONE IS GONNA TEACH ME HOW TO IMPROVE A ROM". Self learning needs lots of trial and error. So we building many ROMs. If you don't like that or you are a cry baby who cries for "XXXXX is not working" or "Poor XXXX". Just stick with STOCK ROM. XDA is for Learning and Not Only for SERVING YOU A BUG FREE, FULLY OPTIMIZED, FULLY FEATURED CUSTOM ROM for FREE.
Sorry.... if anything hurts anyone... I mean it.
Click to expand...
Click to collapse
Why did you took it personally lol? it was just an observation. yes there are people who want to learn and they have to start somewhere. nothing wrong in that. but when you see same people doing exactly same thing for a long time and not improving upon that. it becomes clear what they are doing.
and i never ask for fix this fix that, cuz i know who are actually developing and who are just waiting for fix to be developed by someone else. so no point asking. you sound like someone who wants to learn. but that doesn't mean everyone else is like you. there are people who as i said haven't learn anything but just copy paste cherry-pick for donation money. i rarely see anyone with their own piece of code. happens even more with kernel btw.
and yes i have compiled cm13 2 year ago that's the reason why i know this, and currently using my own (copy-paste haha) kernel for both MG5/nexus 5x. although i haven't released it. nor i'll. (source is on my git if you don't believe).
Anyway, best of luck for your learning, i hope you will learn a lot and will be able to fix problems by yourself instead of waiting for others. it's a long road ahead :good:
First of all, people always mistake ROM/Kernel etc development (not talking about app and other development which are indeed) as profession of devs, they do it in their FREE time because they like it, for example you play basketball because you like it.
Secondly, when there is shortage of ROMs, you yourself would complain about it, please correct me if I'm wrong. Different ROMs have different flavours, and everyone of us likes tasting different flavours. If you're worried about why a thread owner isn't updating it, you can migrate to other one instead of complaining about it.
Some guys have enough skills to compile ROMs, but not the ability to work on source code. So they wait for fixes by those who work on source, and update their ROMs as soon as bug is fixed. Also, compiling can be the start of learning development for guys.
Although I agree with @kraatus90 on some points, there are some things that I don't. First of all, there's no point of redoing the whole kernel, vendor, tree source stuff when you can use the available code with some modifications, obviously the one who uses it have to give proper credits to the bringup dev and other contributors. Also it should be moral duty of the forker to improve the forked code, be it in small or big ways. Simply forking, compiling and PUBLISHING is certainly disheartening and condemnable.
Related
I've got thick skin so feel free to throw things.
Watching the forum over the last month I've seen a proliferation of ROMs to the point that I've stopped updating - also partly because my favorite and second favorite teams have stopped putting out new versions. I finally succumbed to the burning urge to try another ROM last night but ended up with buyers "meh."
The ROM environment has become so fragmented that it's hard to know what the advantage of ROM a is over ROM b other than appearance.
A comment from one of the ROM makers brought the problem into sharp focus. "I've renamed my ROM because I didn't know one of my team members already had a ROM named X."
How can you be part of a "team" and not know what's being produced by that team?
It seems like we've got more themers producing work in the form of full ROMs rather than themes. I've got nothing against themers, I love packages that can completely change the look of my device and I'm always on the lookout for cool new themes.
I'd rather see ROM maintainers and themers working together where the former group produces faster and more reliable ROMs while the latter group produces mods for those ROMs.
Do the two groups just not want to work closely together or are there predominantly just mostly lone wolves working at the ROM/theme level in Android?
Wrong section. Suppose to go in q&a (QUESTIONS and answers)
Sent from my SGH-T959 using XDA Premium App
I disagree because it's directly applicable to development and is aimed at the developers. It's not a general q/a question
I agree with this. There's no need to make a "rom" if you just change the theme. Just make a theme and zip it up then post it in the themes section. And oh yea I believe people refer to these people as "winzippers".
Sent from my HTC Glacier using XDA App
OP has a great point about our forum here. Ive really stopped doing anything but for my own use, and with the exception of a few real roms put here, I've watched our Vibrant area here turn into a rom porting paradise, without a lot of original work done by people calling themselves devs. Several of these self proclaimed devs have asked me for help with recent projects, and have then been unable to provide even a simple logcat for diagnosis. If someone cant pull a logcat or understand how to do other basics, you really need to take your time and learn.
It is okay to theme and do little things while you learn, and take the time to put out a quality product, instead of a hurried build thats half broken. We have a slight handful of true devs out here, and a whole bunch of people who want to learn, but seem to be in too much of a hurry to kang others work and not really learn how to build a rom from the ground up. Its a damn shame.
Ginger Clones of the World Unite!!! via the XDA App
I agree with Br1cK'd. There are a lot of "devs" lately that seem to be kanging together half broken ROM's. I can't tell you how often lately I've flashed something only to find major bugs, when the OP claims that the ROM is 100 percent working and bug free. It seems that most of the more skilled developers have moved on to newer devices. I'm all for people learning but they need to do a lot of quality control before they post their work on XDA.
are you tryna say my team member ferhanmm that did an error ? whats up with you son?>
But then... what actually constitutes a "Rom".
For as far as I know, according to CM6/7/Miui people, only theirs are truly "Roms", as they are built from ground up.
Everything else is just a themed stock Rom, or improvements to existing Sammy framework. (Which I still love btw)
If there were malicious Roms that are purposely bricking systems, then I would argue for stricter requirements for releases. But as it stands, I think the openness of this forum allows users and developers alike to find what makes them happy.
I just think in general, Rom devs/maintainers get more credit (Thanks button hits?) than purely themers. As there is a feeling that themers kind of "work for" Rom Devs... Which is why people tend to package their work as Roms instead of themes (So their work seems less derivative or what not)
Wrong section, but I agree.
Sent from my SGH-T959 using XDA Premium App
Br1cK'd said:
OP has a great point about our forum here. Ive really stopped doing anything but for my own use, and with the exception of a few real roms put here, I've watched our Vibrant area here turn into a rom porting paradise, without a lot of original work done by people calling themselves devs. Several of these self proclaimed devs have asked me for help with recent projects, and have then been unable to provide even a simple logcat for diagnosis. If someone cant pull a logcat or understand how to do other basics, you really need to take your time and learn.
It is okay to theme and do little things while you learn, and take the time to put out a quality product, instead of a hurried build thats half broken. We have a slight handful of true devs out here, and a whole bunch of people who want to learn, but seem to be in too much of a hurry to kang others work and not really learn how to build a rom from the ground up. Its a damn shame.
Ginger Clones of the World Unite!!! via the XDA App
Click to expand...
Click to collapse
first of all about the logcat ? did you learn alone ? i guess that if someone ask you, its nno bad to help is it ? because i bet some one showed you...now about the kang, so almost every rom here is a kang right ? almost all roms based on stocks from i9000s and stocks kb1`s isnt it ?... i guess this people have the right to learn, but seems you guys that already know a little dont like to help huh?
I have more than enough mods on my rom to constitute it not being a theme, and I don't know about you but I don't memorize every rom name out there. It sounded similar so I changed it, what's wrong with that? Since 2.2 has already been tweaked to the max I was able to put out a pretty stable version in the first post. Only things I can really do from here are make it more efficient and finish the theme which I plan to do but I just posted it. And it's my first rom so thanks for the encouragement.
I agree, the forum is filling up with "roms" that are just the same rom rethemed over and over and over again. What annoys me most are these self-proclaimed "devs" who take bits and pieces of other people's work and put them together for their own "rom" when they didn't really write any of it. Just take a look at their credits lol... It's a crazy long list.
I don't think there's anything wrong with having multiple ROMs. After all, everyone will like something different.
I think what the OP is saying though is that there are ROMs out there are essentially the same pieces with different theme, or maybe a new lock screen, and whatnot. I think the OP means little additions like that can be part of a theme or the theme & apps forum and could be added to any ROM and doesn't warrant releasing a new ROM under a new name and new dev.
jimmynguyen91 said:
I agree, the forum is filling up with "roms" that are just the same rom rethemed over and over and over again. What annoys me most are these self-proclaimed "devs" who take bits and pieces of other people's work and put them together for their own "rom" when they didn't really write any of it. Just take a look at their credits lol... It's a crazy long list.
Click to expand...
Click to collapse
as my partner said above, hell son you dont undestand, everybody uses tweaks that are made because there is no need to redo it...name me any rom you have created ? do you know about roms? dont be stupid
ColorNapkin said:
I don't think there's anything wrong with having multiple ROMs. After all, everyone will like something different.
I think what the OP is saying though is that there are ROMs out there are essentially the same pieces with different theme, or maybe a new lock screen, and whatnot. I think the OP means little additions like that can be part of a theme or the theme & apps forum and could be added to any ROM and doesn't warrant releasing a new ROM under a new name and new dev.
Click to expand...
Click to collapse
+1
Sent from my SGH-T959 using XDA Premium App
I did my first root about two month ago. Since then I have tried about 20 various roms or updates to them. I tried one last week that seemed to be a copy from an established developer. The other team got really pissy and used alot of immature slang when confronted. I will no longer use any roms from them. I agree that people should learn from the ground up before posting roms and stop the plagiarism.
I appreciate the hard work of the legitimate developers on this site.
Sent from my SGH-T959 using XDA App
ferhanmm said:
I have more than enough mods on my rom to constitute it not being a theme, and I don't know about you but I don't memorize every rom name out there. It sounded similar so I changed it, what's wrong with that? Since 2.2 has already been tweaked to the max I was able to put out a pretty stable version in the first post. Only things I can really do from here are make it more efficient and finish the theme which I plan to do but I just posted it. And it's my first rom so thanks for the encouragement.
Click to expand...
Click to collapse
dont pay attentionn to this ppl fer.. day just stupids ... look at thhe quote i made above.. its just stupid, they want us to redo the same **** that is already made... for example.. whats the need to do a gps fix when jellette made one already ? its just stupid
them may be half a$$ed devs but them gotta have donate button
Bosina & Br1cK'd, first, thanks for your input and participation but this thread isn't about helping or not. It's about packing up thematic changes and publishing them as a ROM rather than a theme bundle.
If a group of members wants to debate about newbies not giving as much as they get, please start a new thread.
bosina said:
as my partner said above, hell son you dont undestand, everybody uses tweaks that are made because there is no need to redo it...name me any rom you have created ? do you know about roms? dont be stupid
Click to expand...
Click to collapse
this dude ha ha shut up im trying to read and your comments are unnecessary and full of hate and You act like You are a Big Time developer who dont take s**t from anyone , go smoke something and relax , i dont see Team Whisky complain or Eugene, just You big time savior .
But if the teams join there will be more people to split the donation money between so maybe thats why people stay separate ?
Well, there are only two kernel developers here in the P500 forum, franco and fserve. There is no doubt that the work both of you have done is off the charts, tweaking every little thing that can be tweaked to such an extent that there hardly is anything left to tweak. And there is no doubt that most, if not all, of the people using your kernels love the work you guys put out.
With that in mind, however, there are a couple of things (specifically bugs) that we request, not demand, to be fixed. As we all know, our phone is affected by two things that I, as well as many other users, believe are two major bugs: the cpu spiking to 100% when touching the screen and the axis inversion bugs. Even with both of your kernels as good as they are now, these bugs hinder their true capability, thus hindering the phone's true capability. Both of you might just be thinking, "Well, there is paolo's kernel, go use that." And as kernel developers, you have every right to think that and decline this request. But seeing how good both of your kernels are, why not make it better?
Please consider this, as many of us believe both of your kernels can be made better with these bugfixes.
The poll is there as an estimate and measure of how many users believe that these bugfixes will make your kernels better.
sweetnsour said:
Well, there are only two kernel developers here in the P500 forum, franco and fserve. There is no doubt that the work both of you have done is off the charts, tweaking every little thing that can be tweaked to such an extent that there hardly is anything left to tweak. And there is no doubt that most, if not all, of the people using your kernels love the work you guys put out.
With that in mind, however, there are a couple of things (specifically bugs) that we request, not demand, to be fixed. As we all know, our phone is affected by two things that I, as well as many other users, believe are two big bugs: the cpu spiking to 100% when touching the screen and the axis inversion bugs. Even with both of your kernels as good as they are now, these bugs hinder their true capability. Both of you might just be thinking, "Well, there is paolo's kernel, go use that." And as kernel developers, you have every right to think that and decline this request. But seeing how good both of your kernels are, why not make it better?
Please consider this, as many of us believe both of your kernels can be made better with these bugfixes.
Click to expand...
Click to collapse
Agreed
PES2012 is hard to play with the lags but suprisingly Pes2011 does not have lag...I read once that Sippolo said its a 2 minute fix for the cpu spike bug
i think its ok to fix bugs even when most users can profit.
but, what about users who have new/other phones now?
i know from franco he's not developing on .35 currently because he has a new phone
and the P500 is used by his father - no way to develop on every day. the next reason is as we
all know, the P500 is a nice device for android beginners but most of us have seen
the new things like Nexus S, Galaxy S-2, HTC devices or other high end phones. I'm sorry
to say that but the P500 is some old and almost used in countries where such high end
devices cant be payed for, or, in most cases too - most users who bought this device
are very young (when i think how old i'm) - and, good developers have a real job to get
enough money for high end devices ... so, these developers cant support such low budget
devices all the time.
For me this means, i'm developing on P500 because its most funny for me to see all these
**** LG hardware bugs, but decided too that there is no way to develop on P500 the next year
too, so the next phoenix-android gingerbread will be the last release for the P500 device too.
I dont know what mik_os is doing, i think he has a real job too and no time to develop all
the time for this device ...
But, ok, these words sounds very sad for most users - i think, there are other ways or users
who take the developers work and can support such devices for a few months. for me it
doesnt matter if users are coming to me and asking how they can develop on my code.
Android should be open source, that means for me there is a community who want to develop
on - and not everybody is a real developer but can learn something, and that can only be reached
with help and understanding each other. Everybody can say "I want Gingerbread on my phone, i want
ICS on my phone, i want a hell kernel on my phone" - but these work cant be developed by google,
its the task for the community, so lets start here and now and stop crying for franco, fserve, mik or
others! Learn to help your self! Be a part of a real community!
I understand what you are trying to say andy, and after reading your post, i must say that i have to agree with you.
As much as I want to start developing myself, I have no idea where to begin. Just a question, which language must I learn to start android development? (is it java or c++? ive seen both languages mentioned but i do not know which one. is there one specific for roms and one specific for kernels? because i think i might give kernel development a try once i learn the appropriate language)
sweetnsour said:
Ah, this thread was short-lived
I understand what you are trying to say andy, and after reading your post, i must say that i have to agree with you.
As much as I want to start developing myself, I have no idea where to begin. Just a question, which language must I learn to start android development? (is it java or c++? ive seen both languages mentioned but i do not know which one. is there one specific for roms and one specific for kernels? because i think i might give kernel development a try once i learn the appropriate language)
Click to expand...
Click to collapse
Developing on android doesnt mean you have to write code by yourself all the time.
Sure, its good to know about C/C++, Java, Shell scripting, makefile reading/writing and other things
but in most time we can copy or integrate existing patches. So, you only know about the bug and
where to fix it with what programming language. For the first time, search for the bug on google
and/or github - with some luck users can find a fix that needs only to copied in the local code.
To start developing on android, its a good choice to understand in details how android is working
and even a good thing is to know about Linux. On windows, you cant develop on Android OS so
you need at least a small Ubuntu/Linux Mint/RedHat or SuSE system with compilers and Java installed.
The next required knowledge is to know how Android is interacting with files:
What is Java for, what is C/C++ for, how Android is booting and what are JNI libraries.
We can open a thread so we can explain something or users can ask for specific things there.
andy572 said:
Developing on android doesnt mean you have to write code by yourself all the time.
Sure, its good to know about C/C++, Java, Shell scripting, makefile reading/writing and other things
but in most time we can copy or integrate existing patches. So, you only know about the bug and
where to fix it with what programming language. For the first time, search for the bug on google
and/or github - with some luck users can find a fix that needs only to copied in the local code.
To start developing on android, its a good choice to understand in details how android is working
and even a good thing is to know about Linux. On windows, you cant develop on Android OS so
you need at least a small Ubuntu/Linux Mint/RedHat or SuSE system with compilers and Java installed.
The next required knowledge is to know how Android is interacting with files:
What is Java for, what is C/C++ for, how Android is booting and what are JNI libraries.
Click to expand...
Click to collapse
Thanks for the info! I will keep this in mind.
andy572 said:
We can open a thread so we can explain something or users can ask for specific things there.
Click to expand...
Click to collapse
good idea (this sounds like sticky material)! would you like to open it? it would not make sense for me to open it since I'm not a developer
First of all i would like to thank andy, mik_os, franciscofranco, fserve, ciaox,knzo, docotornotor and many others who i may have forgotten for their impeccable work towards this community and for working their asses off. You'll are invaluable assets to the community and i could'nt imagine using my phone without you'll.
Reading andy's post i must have to agree with him because you devs have worked so hard towards our phone even though many of you''ll don't own one. Also you bared with the many spams, useless comments on your threads without saying a word. Also many of you have jobs in RL for which you have to work hard, and developing for a phone which you don't even own/primitive phone would seem to you as a waste of time and i can thoroughly understand that. Even though i dunno scat about developing, i do know that it is highly time consuming and resource oriented.
So as you'll probably know that the 2 most irritating bugs on our phone are the touchscreen driver lags, and the axis inversion bugs. Me, as well as thousands of p500 users can't thank franciscofranco and fserve for their dedicated work towards our phone and for developing two awesome kernels which made our p500 superfast. Any p500 user could match his phone's performance to our higher end phones and show its capablities off even though it being a low-ish end phone. I think i am speaking for the thousands of p500 owners all around the world and i would like to take this opportunity to request you kernel developers to fix these bugs and include them in your fanstastic kernels. India itself has the largest number of p500 owners all around the world and this phone is still popular as of today and if you'll didn;t know it is THE BEST SELLING SMARTPHONE phone in India. Therfore tons of us users would love if u fixed these two final bugs as they in my opinion are the biggest performance drainers all credits to ******y LG developers. As sweetnsour said, you devs have every right to decline this request as there is already the paulos kernel and plus you devs have worked your asses off to tweak our phones to its fullest extent and i don't think there may be any more tweaking left to do
However i do believe you devs collaborate in this one final project. Me, as well as every member of this community can't thank you enough for your hard work! We also have many talented devs [ciaox is 13 wtf? ] who can continue development of this phone. Looking at the dev section, many new roms have come up since mik's cm7 port and each rom outperforms the other[no disrespect to mik_os, he started the cm7 era!].
I hope fserve and franciscofranco take this post in regard and work towards fixing these bugs !
Thank you.
ps. sorry for my bad english.
@ andy572
Open ur own website and tell us more! I wanna build my own ROMs but i kinda fail it... With ur small free time? Can u exxplain?? It would be grateful to others!
Sent from my Nexus One using Tapatalk
Uhm... Fserve has already patched his Goldenleaf Kernel with Der_Caveman + Waleedq + Sippolo's workaround to fix axes inversion and cpu spikes.
The related Fserve's kernels are Goldenleaf 111107 and 111108 (I prefer this one). Cheers!
if u didnt know, axis inversion is not possible to fix 100% because it is a hardware issue.........
there is only little you can do about it in the coding part
Yes, I know it's an hardware problem, however a workaround is better than nothing!
Sent from my LG-P500 using XDA App
for me it
doesnt matter if users are coming to me and asking how they can develop on my code.
Android should be open source, that means for me there is a community who want to develop
on - and not everybody is a real developer but can learn something, and that can only be reached
with help and understanding each other. Everybody can say "I want Gingerbread on my phone, i want
ICS on my phone, i want a hell kernel on my phone" - but these work cant be developed by google,
its the task for the community, so lets start here and now and stop crying for franco, fserve, mik or
others! Learn to help your self! Be a part of a real community!
Click to expand...
Click to collapse
well said~
fserve's goldenleaf has added Sippolo's workaround
For me as a user, i would say THANK YOU to you guys for bringing this community alive. Thank you for your hardwork and effort that you put in. I would say that my p500 runs fastest than galaxy s stock 2.3.3. Im not joking as my phone is smooth thanks to you guys. no bugs for most of the roms i tested. I may not be a dev but i understand a lil bit. So once again thank you guys
Sent from my LG-P500 using XDA App
I agree with most of what Andy said, except the part that our phone is obsolete.
I'm not a dev but I found plenty of tutorials available that explained how to successfully compile a kernel from source and extract a .config from an existing kernel. I never found a perfect how to but by meshing various methods together I was eventually successful. After reading francos github commits I discovered the toolchain he was using which was the final ingredient.
From there I used a diff tool to compare franco and Paulos sources, this is how I found the camera flicker fix. When I saw big differences in the source I googled it and/or copied it over then compiled and tested it. It took about 5 tries before I found the flicker fix. This learning process took more than just a couple of hours, it was frustrating but eventually rewarding. I still don't know anything about C or Java, so Andy is right, read/research, copy/paste, trial and error actually works.
Considering that Paulos kernel has resolved these issues and franco hasn't means you should be able to use the same technique. These bugs seem to affect gaming the most, which I don't do, so I haven't had the motivation to look into it.
franco and fserve are more than willing to include fixes. fserve posted a test kernel that included my find within a day. Within a week franco had released a new version that included it.
Open a discussion thread, I think it's a great idea! This is a developers forum after all. Thousands of noobs should be able to combine their efforts to fix these issues. Let's make it happen instead of waiting for it to happen.
Thank You !!!
Suggestion : Why dont Fserve or Franco use and edit Paulo's V6 Kernel'?
is it possible'?
OT.. .
Mistakes are the PORTALS of DISCOVERY .. .
so Cmon.. . Lets commit mistakes
Why don't ask them yourself?
Btw: PaoloM70's 2.6.35.14 V6 Kernel source:
http://www.multiupload.com/18Y712HS9G
so there is no multitouch bug and screen touch lag in paolao kernel?
@sweetnsour . I feel like Ciao X would be a good person to ask about this one. He is young so I feel will continue to work on our p500. I could be wrong. But I also think you could learn much about your goal( which by the way I think it's WONDERFUL you want to learn to develope ) I KNOW I'm not cut out for it, and so I can be honest while I am no actually HELP to this community when it comes to developing. I AM. A HUGE fan, supporter and appreciate of all the passion and art and great works that come out of this wonderful community!!! Anyway, I digress CIAO CAN YOU WEIGH IN ON THIS???
Optimus T
OpenOptimus (froyo)
latest franco kernal
748/480
Interactive X
Jonny Green
"im not a Dev but I flash alot"
TL;DR
If you want to help me, post on MY thread about my kernel bugs. --REALLY--
(or dev something, lol)
(or donate me, i really love that )
FOR NOW, i need people to tell me which is the WORST game to play on p500 using gbs v19 kernel, AND it need to be free (or not if you give me the money).
So i can test this touchscreen bug.
Please, post, on my thread for .32 kernels and on franco thread for .35 kernel.
Thanks
fserve said:
TL;DR
If you want to help me, post on MY thread about my kernel bugs. --REALLY--
(or dev something, lol)
(or donate me, i really love that )
FOR NOW, i need people to tell me which is the WORST game to play on p500 using gbs v19 kernel, AND it need to be free (or not if you give me the money).
So i can test this touchscreen bug.
Please, post, on my thread for .32 kernels and on franco thread for .35 kernel.
Thanks
Click to expand...
Click to collapse
Thanks for weighing in! There are two apps you can try using:
For a game, try playing glow hockey (use the two player mode). When your fingers cross, you will be controlling the opposite puck.
To see what is really going on, check out the app "multitouch vis test". You will see the bug when you cross your finger either horizontally or vertically.
Sent from my LG-P509 using xda premium
EDIT: I was talking about the axis inversion bug, not the CPU lag bug. Not sure what the worst free game for that would be, but neocore would be good for testing this bug.
What you ppl think about this:
"I do NOT give permissions to anyone to use anything from this ROM in your own ROM."
Do this means I cannot use that roms kernel which he take from other ROM??? Or he mean that he build that kernel or core stuff himself?
gintsgints said:
What you ppl think about this:
"I do NOT give permissions to anyone to use anything from this ROM in your own ROM."
Do this means I cannot use that roms kernel which he take from other ROM??? Or he mean that he build that kernel or core stuff himself?
Click to expand...
Click to collapse
where did you see this? link?
gintsgints said:
What you ppl think about this:
"I do NOT give permissions to anyone to use anything from this ROM in your own ROM."
Do this means I cannot use that roms kernel which he take from other ROM??? Or he mean that he build that kernel or core stuff himself?
Click to expand...
Click to collapse
if you are going to release a rom on xda and going to use parts of someone else's rom then he does not give you permission for that. if you are going to use parts of someone else's rom but it is for your own pleasure you can go ahead and do so if you want. hope that makes it clearer
Stifler69 is right. As long as it's home use only and you don't claim its your own work and promptly publish it you should be fine.
Dc
Sent from my GT-I9100 using Tapatalk
A its a question ,
B i use roms and kernels from many sources in my phone but i am not posting so its not a problem .
C if its your own phone and not posted who knows what you use
D you can not then moan or ask for specific rom help if you have changed the original components .
I use xx rom but a different kernel own CSC and ICS modem .
jje
i know where that is from. it's fine as long as you don't publish what you took and claim it as your own.
i can understand why he is being this way. he spent time and effort trying to bring all of those features to his rom and people just take them, put them in their roms and don't even bother giving him credits. i even read once a foreign forum mod copied his whole rom and just renamed it then published it as his. you can imagine what he felt. yet he still let them go. then he got reported (reason unclear) by a rom dev who was using his work and got banned. that's why he's now doing what he's doing.
anyway, i'm sure you can find out more details from the android dev forum if you look hard enough.
Personal use is fine, but you can't go re-posting it, or trying to sell it for donations etc...
Basically, it's common courtesy, that person is simply saying they don't want people kanging them.
Yes. I can understund him. I can understund about his artwork or somthin. But still...
Why I cannot reuse some parts... probably open source ones? He does not do that? Where is that line when Open source components becomes his property?
PS. I have worked on a lot open source projects... and I will never ask for credits. It's fine if you get some.
PSPS. Do he recognise how much open source projects put they work on making that rom to work at all?
I understand your point, but that's the rules of XDA (rule #12). And those we accept and agree when joining the forum.
Sent from my GT-I9100 using xda premium
Well the linux kernel used by all ROMs is GPLv2 licenced, so no one has any right to say that anyone else cannot reuse it, and they have a responsibility to release their source code if they modify it.
As for the rest of the ROM, asking people not to use its contents seems a bit unreasonable and disingenuous to me. All the ROMs people release here are the culmination of all the work others have done, and include lots of stuff that other people have shared freely.
This article appeared today on the main page of XDA and I feel that it's a very important lesson for any/all new ROM devs.
Sage Advice from Cyanogen Still Valid Today
http://www.xda-developers.com/android/sage-advice-from-cyanogen-still-valid-today/
Excerpt:
He had this advice to offer for those looking to make their own Android ROMs:
Stop. Write an app or two first, learn how the system works from a developer standpoint. Learn some Java. Read the developer documentation. Learn how to use Git. Then learn how to build AOSP from source. Read the porting guides, and learn how the build system works….. Now try to put your new found skills to work on enhancing the platform by writing code or making theme overlays. And share! And put that s**t on your resume. There is a *ton* of information out there but any kind of “step-by-step rom cooking guide” is going to be a complete fail- it’s too broad of a subject.As XDA has grown right along with the meteoric rise of Android, so has a desire of users to create their own ROMs, kernels, themes, and so on. Much of this work classifies as “original development,” but there’s been a growing trend to what many are calling “derivative development.” This category covers most of ROMs based on stock releases from the manufacturers, applying patches and scripts aimed at optimization, theming and/or removing stock applications, and using “kitchens” that run a stock release through a list of scripts and then repackage as a recovery-flashable update.zip. This is what Cyanogen was expressing frustration about—shortcuts being taken to achieve a product that differs only slightly from stock (derived) and pushed out instead of building from source and delving into the core of Android and making something truly original.
XDA-Developers exists first and foremost for developers. It’s at the core of who we are; it’s in our blood; and it’s in the air we breathe. There is a place for derivative works—they provide an entry to the scene which can help to introduce people to the wonders of Android. But let’s not stop there. Don’t be satisfied with just creating yet another derivative of someone else’s work. Instead, follow Cyanogen’s sage advice and learn about Android from the ground up, and create something truly original and innovative.
Click to expand...
Click to collapse
Guess I should continue with this hello world app... haha
Op just explained 99% of our roms lol
Repackage, rename, reskin and ask for donations. Rinse lather and repeat. Now your a dev!
Ha.
True software developers understand the wisdom of code reuse.
So ,in my opinion, if a fledgling developer takes a set of code and applies addons, makes a few setting changes then calls it a ROM and provides users benefit...then they are on the path.
Sent from my SAMSUNG-SGH-I717 using Tapatalk 2
andrawer said:
Ha.
True software developers understand the wisdom of code reuse.
So ,in my opinion, if a fledgling developer takes a set of code and applies addons, makes a few setting changes then calls it a ROM and provides users benefit...then they are on the path.
Sent from my SAMSUNG-SGH-I717 using Tapatalk 2
Click to expand...
Click to collapse
Even if they fail to write a single line of original code?
I'm with cyanogen on this one...
saddly alll this is sementic
if the world of android was perfect then this would be true .by perfect i mean everything being open source ...
but if everything was open source we woudlnt have things like arc touchwizz blurr or sense , it is my opinion and shared by many others that android would be very boring if we only had aosp .
what does a coder brings to touchwiz sense or blurr device ?
the market is filled with cool apps and launcher .. 99% of them coders will make apps for android and wont bother with anything else
that brings me to my next point . building from source means on top of aosp , or in my terms vanilla android .. many devs love vanilla and its fine but what about those who dont ?
99% of the rom on xda are just that : either source compiled with apps added or stock deodex rom with a theme and apps added ..
here is the but , and before i say it i wanna say everyone is entitled to his opinion and im not bashing anyone ,
without guys like me who just hack the code and spend countless hours looking at what the code is actually doing and port the nice stuff from sense to TW or form CM to TW and RE (reverse engineer all these nice codes) 99% percent of the android devices would be boring because lets face it there is only one aosp device / year..
so from what Cyanogen is saying we should all buy a gnex and stop supporting those that make android close source,
but wait without them , many things woudlnt be in CM in the first place , what is cm without all these kangs? a glorified aosp ?
ok maybe im pushing but you get my drift...
how many true innovations by Cyanogen vs them Proprietary UI ?
fun fact the head (or ex ) of Cyanoen now works at samsung and help make touchwiz better (close source)
what about miui , they have so many innovations , and they dont share any of there code ..
so as I said there is no black or white here
thats what android is all about make your own thing play with it call it yours and make it a hobby , and maybe just maybe others will like it ...
I have seen way to many devs get god like status on xda for deodexing a rom and injecting voodoo in there kernel (for example)
i ve seen crazy talented themers have there work taken by others be ignored by the community and then vanished , and everyday we see a kik ass true developper on here and treat him like hes a nobody , because he doesnt have or because we havent heard of his rom .....
i completely understand where cm is coming form but my opinion differs slightly ..
@op kik ass thread (as I never read the front page)
Hard to build an i717 ROM from scratch with all of the proprietary bits, Samsung framework, etc, as most of that is proprietary as DAGr8 says. AOSP/AOKP works, but lacking some SPen functions and still relying heavily on a binary kernel as there are no kernel sources for ICS yet.
Hopefully the kernel situation changes, and we're back to the normal business of everything except the proprietary blobs that have to get copied from a stock ROM......
It'd be nice if all required code was released, but for some reason such things tend to be considered proprietary. Oh well.
Thanks OP. I also don't read the frontpage near often enough.
I like what Cyanogen is saying, and agree with his points from his developer point of view. I also agree with DAGr8 and his points. The fact is that Android gives us so many choices and has so many options for exploration. I think that's why so many of us have moved to the Android ecosystem. There is enough room for everyone. Android is the most prevalent mobile OS in the world for a reason. We can all have our opinions. We can all have what we want on our devices. And there are more and more people willing and able to jump in and try to build. Call them developers, or hackers, or derivators. It doesn't matter to me. They all add value to Android.
Hi,
I've been using XDA for a while now, and with the help of many amazing devs I've managed to flash custom roms to all my older devices no problem! Recently I've been waiting for a dev to make changes to an existing kitkat rom, to fix a bug and I'm becoming a little impatient. I know everyone has their own lives to attend so I'm not complaining, rather I'd like to try and help this dev with the problem as I have quite a lot of experience with Android apps. I've read up on the CM wiki the sort of things that are involved in debugging roms etc. so I know that I'll only be able to help with the framework (as I know no C/C++).
So my question is, are there any ways I can help them, and will my help be appreciated considering the skills I have? I also have a decently fast computer too so I have a feeling I could help with building the rom.
Thanks.
Roarster31 said:
Hi,
I've been using XDA for a while now, and with the help of many amazing devs I've managed to flash custom roms to all my older devices no problem! Recently I've been waiting for a dev to make changes to an existing kitkat rom, to fix a bug and I'm becoming a little impatient. I know everyone has their own lives to attend so I'm not complaining, rather I'd like to try and help this dev with the problem as I have quite a lot of experience with Android apps. I've read up on the CM wiki the sort of things that are involved in debugging roms etc. so I know that I'll only be able to help with the framework (as I know no C/C++).
So my question is, are there any ways I can help them, and will my help be appreciated considering the skills I have? I also have a decently fast computer too so I have a feeling I could help with building the rom.
Thanks.
Click to expand...
Click to collapse
Ask them. Or ask their permission to use their ROM as a base, make some actually meaningful modifications, and release it. But as too your "skills" I didn't see you state what they were, and if you have to ask then probably not. Don't stop reading/learning though, you'll only get more knowledgeable.
thewadegeek said:
Ask them. Or ask their permission to use their ROM as a base, make some actually meaningful modifications, and release it. But as too your "skills" I didn't see you state what they were, and if you have to ask then probably not. Don't stop reading/learning though, you'll only get more knowledgeable.
Click to expand...
Click to collapse
Ok, I was thinking along the lines of making modifications and then pushing them to a git repo. Maybe they don't have one, I'll go ahead and ask. As for my skills, I was saying in my last post that I have quiet a lot of experience developing Android apps. Do you know what % of rom editing is Java based vs C/C++?
Roarster31 said:
Ok, I was thinking along the lines of making modifications and then pushing them to a git repo. Maybe they don't have one, I'll go ahead and ask. As for my skills, I was saying in my last post that I have quiet a lot of experience developing Android apps. Do you know what % of rom editing is Java based vs C/C++?
Click to expand...
Click to collapse
There is no hard/fast guide on what "rom-editing" is. Are you wanting to contribute to kernel development? Better know a lot of C. Wanna roll a cool application for a ROMs special settings? Java is what you want. What I'm getting is you know more Java, so why don't you write and application that you think will solve a problem, then talk to a developer about including it in their ROM?