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.
Hey Guys!
This thread is basically there to announce, that i will stop with baby modding
There are a few things i will tell you
1st: I will STOP with develop UMX-Android for CM7!
2nd: I will recreate UMX-Android COMLETELY new!
3rd: UMX-Android will be based on "OWN COMPILED CM9"!
4th: It's my first try to compile, so don't be afraid if everything takes longer than planned!
5rd: UMX-Android won't be based on this Colorful theme from now on!
A few answers to the questions you might ask:
"Why do you stop development with CM7?"
-Because CM7 get's old, a little bit to old for me personally...
"Why don't you develop with CM10 or CM10.1?"
-Because i have the felling, that when android gets a version higher, it needs 50mb more ram to work fine! I will !!!TRY!!! to tune up CM9 so heavy, that it will be as smooth as jelly bean on SII or something like that(not really but i try to get it as fast as i can...). As well there are no official 4.1 OMX libs for armv6, even with good porting, i'm afraid that everything will not work as nice as official
"That's again any from these phrases which you tell us everyday..."
-No, i will stop with this baby modding, and if i'm to dummy to compile a at first booting up rom, i will stop with develop completely(maybe )
If you got more questions, just ask i will tell you everything about my plans more infos will come in this hread soon
Bye,
Glenn Töws(aka GlenniBoy)
Was this worth a whole new thread?
Maybe yes, maybe not, i've simply did it that everybody can see this because i think that many people think i'm a nooby developer and i just want to say that i want to start with a new world of development(for me personally)
When the jb kernel sources came out i was hoping development would speed up and attis would release a cm 10.2 build with jelly bean kernel but instead the speed of development has remained the same when jb kernel sources were'nt released.
And DONT give me crap devs are trying their best and they will release it when they want to a lot of people like me were keen on seeing are builds in cm10 and other builds progress faster when kernel soources for jb finally came out all am asking is devs such as attis plz try and boot with jb kernel and update cm 10.2 soon so our community can become lively again THANKS.
Sent from my HTC Desire X using xda app-developers app
This post means you don't follow atis112'work on github, just go there and you will find your reply.
xpirt
Wohohoh,
it's not your lost-big-amount of time...
Delete, report as spam...
Sent from my HTC Desire X using xda app-developers app
Well, this is a rather useless post isn't it? All you're doing here is begging for new builds once again, and even being a tad rude.
I'm sure atis works on it when he wants to, and since we aren't doing anything (except for the beloved neXus PRIME and prototype-U - sorry if I forgot others -) it's way more than enough.
And you say, "don't give me that **** about ETA etc." (Not the exact quote) don't you? Now, that most likely means you have been in touch with people saying this to you, probably because you also posted words like these on other threads. People would think you would've learned from that, but from looking at this I draw a rather different conclusion. And that's something that makes me a little bit sad.
I know you're a fan of atis112, and I know you're not trying to be rude in any way by posting this, but don't you think there are better ways of stimulating him to do what he does (even) better? Try donating, or if you're short on money, try getting a closer look into the source code and see if you could help him with doing what he's doing so amazingly good at this point.
Sent from my awesome fridge
And I'd like to remember that atis112 is building CM for him, because he wants to have it, then if he share his work with us is another thing and we have to be happy as he is the only one who can bring it us.
xpirt
Thread Closed
These kinds of threads are not useful and often lead to flame/trolling. Therefore they are not allowed on XDA.