Related
Dear all
Got my HTC HD2 today,Need ur help guys to share best working rom without any bugs,I want to dual boot my HTC HD2 with Windows 6.5 & Android
Thanks in Advance
munishjoshi said:
Dear all
Got my HTC HD2 today,Need ur help guys to share best working rom without any bugs,I want to dual boot my HTC HD2 with Windows 6.5 & Android
Thanks in Advance
Click to expand...
Click to collapse
Congrats bro and welcome aboard.
Just wanted to point out, this is the Dev forum, Q&A going in the General Section.
Anyhow, you Have Sense rom, Sense 2.1 and CM7 (no Sense, other ui such as LaunchPro or ADW).
You got too many choice.
Pick which you want to test first and enjoy flashing once you get addicted.
You could also put more than one Android build on your SD card. So you can test more than one at once without deleted the other.
Whichever you choose, Good luck
PS: Most famous are CM7 builds
Thanks Bro for replying
i m not new into flashing..already flashed so many phone..m already flashing addicted...i saw so many roms in this forums...i just would like to know that which one is bugs freeee
Thanks
munishjoshi said:
i m not new into flashing..already flashed so many phone..m already flashing addicted...i saw so many roms in this forums...i just would like to know that which one is bugs freeee
Click to expand...
Click to collapse
Anyone who knows anything about software(or real life for the matter) will tell you - "it does not exist"
You will have a better luck asking what ROMs people are using and would recommend.
it's hard to say which rom doesnt have bugs... try first. i like the rom from MCCM HD 4.0. i'm using it at this time.
I can personally recommend the AmeriCan Android rom, been using it past months and updates makes it better and better ^^
Personally though, uninstall the NetFlix thing right after putting the rom on, it made my HD2 uber slow, the second it was gone, it was back to super speedy
Hi, could somebody please link me the thread where the multiple versions of abdroid is expaned? Thanks
Sent from my GT-P1000 using XDA Premium App
Just buy a HTC phone with Android like DHD.. That is not any bug.
I personally like and use JAGUARMIUI 5.
Sent from my HTC HD2 using XDA App
manhktqd said:
Just buy a HTC phone with Android like DHD.. That is not any bug.
Click to expand...
Click to collapse
I´ve been running AmeriCanAndroid GB2.3.3 on my HD2 for over 2 months now and have less bugs than my friend with a stock (updated) DHD.
I could recommend this one and version 2.3.4. I suggest you try that one and give it a go. I can't imagine that this ROM is not good. Be sure to read the last 10 pages of the ROM thread to be sure. I think that´s the best way to check if the latest version doesn´t have any significant bugs. Good luck!
American android. You wont look back
Sent from my GT-P1000 using XDA Premium App
I have used the following SD Builds during the last 3-4 months. Do not want to switch to NAND as I still have some use for WM. Even tried some of the older RAM builds like Darkstone's SuperRAM Froyo. I am giving my preferences below and check my sig for other info.
1. AmericanAndroid, have tried almost every build since it came out.
http://forum.xda-developers.com/showthread.php?t=957652
The two most recent Builds, 05172011, 05192011 and 05212011 have given me the most issues with significant screen lag and persistent wait periods when using these. I tried them with three different SD cards (4G C2, 8G C4, 8G C6) and still had issues. I am now back to the 05032011 Build which runs superbly on two different SD cards (4G C2, 8G C4). I was surprised to find that the Class 2 SD card was the smoothest although I am sure there are variations based on other factors beyond the scope of my intelligence. Everything works like a charm on 05032011 build except Market acts up sometimes. Follow the link for all Builds by date here: http://uploading.com/linklists/debamfea/ACA
2. May 14 BOYPPC Build
http://forum.xda-developers.com/showthread.php?t=970542
is good too but as is usual we all have our personal preferences and I feel more comfortable with AmericanAndroid. This would be my backup if AmericanAndroid goes loopy.
3. Have used MccMBoxMaX Build too.
http://forum.xda-developers.com/showthread.php?t=1038694
I have kept it on a separate SD just in case. Pretty solid build but I am sticking to AmericanAndroid for the time being.
I have tried at least 8 releases for the past 6 mths. From one chef to another chef. But for the past 3 mths, I m using MCCM SE V3.3 . I must say it is stable n fluid. I have also recently tried other GB version from MCCM n other chefs..... but I guess its not really that stable yet. Probably someone can recommend me a stable GB version. Would LOVE to get my hand on one of em.
this isn't to mislead anyone...i feel i've gotta say.....mccm doesn't compile his builds from source. his is completely reliant on switching files around....i have yet to see anything i'd trust for a second from him. he's had previous problems with actual chef's and even developers because he breaks xda's rules and steals builds....this isn't just a warren dislikes mccm thing.
use those builds if you wish......but those very builds are 100% reliant on the taking of someone elses compiled source. if he at least built from source code, he'd get some credibility from me.
warrenb213 said:
this isn't to mislead anyone...i feel i've gotta say.....mccm doesn't compile his builds from source. his is completely reliant on switching files around....i have yet to see anything i'd trust for a second from him. he's had previous problems with actual chef's and even developers because he breaks xda's rules and steals builds....this isn't just a warren dislikes mccm thing.
use those builds if you wish......but those very builds are 100% reliant on the taking of someone elses compiled source. if he at least built from source code, he'd get some credibility from me.
Click to expand...
Click to collapse
@warrenb213, thx for letting us know about this issue. I wasn't aware of it but will treat MccM's work cautiously. I'm going to head over to the AmericanAndroid thread to give you thanks which I should have done some time ago.
warrenb213 said:
this isn't to mislead anyone...i feel i've gotta say.....mccm doesn't compile his builds from source. his is completely reliant on switching files around....i have yet to see anything i'd trust for a second from him. he's had previous problems with actual chef's and even developers because he breaks xda's rules and steals builds....this isn't just a warren dislikes mccm thing.
use those builds if you wish......but those very builds are 100% reliant on the taking of someone elses compiled source. if he at least built from source code, he'd get some credibility from me.
Click to expand...
Click to collapse
Hi... Warrenb long time no see. How can u give comments without thinking . Any proof that i stealing your build ? In xda rules u can post build if the other dev give u permissions . Just after giving permissions then give fake info to Moderator after u realized that i better tweaker than u . I got ban because of warez , big 'thanks' to u . But at the end just live with it . If u want to give comment think carefully please.
Edit: This is your comment on 'NexusHD2-Gingerbread V2.7 [GRJ22/Android2.3.4][Kernel:tytung_r10]' thread :
Warrenb213
14th May 2011, 09:51 PM
ReTweet this post# 24
I feel like I've got to ask....
Did Tytung approve of this SD-build? I ask because Tytung has experience in this already, I don't know why he/she wouldn't convert the build themselves? lol
Click to expand...
Click to collapse
This is the reply from the man him self :
tytung
15th May 2011, 10:37 AM
ReTweet this post# 29
Originally Posted by warrenb213
I feel like I've got to ask....
Did Tytung approve of this SD-build? I ask because Tytung has experience in this already, I don't know why he/she wouldn't convert the build themselves? lol
Yes, I approve it.
Thanks to HaPeWe for the time and effort to convert it from NAND ROM.
I have no time to install WM just in order to test SD build.
And I won't like to release a SD version without testing.
That's why I don't release it myself.
Click to expand...
Click to collapse
OH man ... feel hurt right
mccmjoon76 said:
Hi... Warrenb long time no see. How can u give comments without thinking . Any proof that i stealing your build ? In xda rules u can post build if the other dev give u permissions . Just after giving permissions then give fake info to Moderator after u realized that i better tweaker than u . I got ban because of warez , big 'thanks' to u . But at the end just live with it . If u want to give comment think carefully please.
Edit: This is your comment on 'NexusHD2-Gingerbread V2.7 [GRJ22/Android2.3.4][Kernel:tytung_r10]' thread :
This is the reply from the man him self :
OH man ... feel hurt right
Click to expand...
Click to collapse
You were banned for good reason, not once....but twice.
You are NOT CURRENTLY stealing the ACA build because the mod's gave you the choice to take it down or be banned. Wouldn't get too confident. Most of the time, including in our case, you acted before getting permission. I wouldn't be surprised to find out most of your "builds" are the same.
If Tytung approved one of your "hack" builds then that is one example where you did in fact get permission.
What you do though in messing with builds has been observed as quite sloppy, and has proved you to be more of a "theme" applier than anything. I have never seen evidence of anything more than a theme applied. You never have shown source code for the majority of your projects, and when you do it's typically been to a place of no actual value for other folks to check out the source. You can't post people to look @ CM code when your using another dev's compiled source which stems AWAY from the stock CM repo's, for example. But the mod's have been lenient in that regard.
I think carefully before I respond, each and every time. I've not said anything which you could refute, mccm. Or was there something I said more specifically about your technique which you wanted to address?
Tweaker? Sir, if that is what you are then we should give folks like you your own subforum under here, called "Tweaked builds from people that have never compiled a build themselves." ACA is a compiled AND tweaked build, and our files can be found in builds across the HD2 forums.
Any developer which would accept the idea that a fellow not building from source code could make their ROM better than they could themselves, would be kidding themselves and they'd know it.
Nuff said, moving on.
warrenb213 said:
You were banned for good reason, not once....but twice.
You are NOT CURRENTLY stealing the ACA build because the mod's gave you the choice to take it down or be banned. Wouldn't get too confident. Most of the time, including in our case, you acted before getting permission. I wouldn't be surprised to find out most of your "builds" are the same.
If Tytung approved one of your "hack" builds then that is one example where you did in fact get permission.
What you do though in messing with builds has been observed as quite sloppy, and has proved you to be more of a "theme" applier than anything. I have never seen evidence of anything more than a theme applied. You never have shown source code for the majority of your projects, and when you do it's typically been to a place of no actual value for other folks to check out the source. You can't post people to look @ CM code when your using another dev's compiled source which stems AWAY from the stock CM repo's, for example. But the mod's have been lenient in that regard.
I think carefully before I respond, each and every time. I've not said anything which you could refute, mccm. Or was there something I said more specifically about your technique which you wanted to address?
Tweaker? Sir, if that is what you are then we should give folks like you your own subforum under here, called "Tweaked builds from people that have never compiled a build themselves." ACA is a compiled AND tweaked build, and our files can be found in builds across the HD2 forums.
Any developer which would accept the idea that a fellow not building from source code could make their ROM better than they could themselves, would be kidding themselves and they'd know it.
Nuff said, moving on.
Click to expand...
Click to collapse
Your right man. Move on! Stop interfere the members that want to share about build.. let them judge by their own.
Banned twice! I make history
U should know the ROM or Build is come from Google we are making it works for HD2. U your self are not builder. Or else u won't be here. U will working with Google.
XDA site is about sharing. I don't mind some one here can come out better build then me. i congrat them. Cause members can enjoy the build daily..
By the way,I being thinking to post up my GB build back here again it will be nice right?
Sent from my HD2 Gingerbread using XDA App
I see this has turned into a bad conversation.
I don't know why you need to quarrel guys, I mean I have no business of meddling but since you've startet arguing I feel I should add a small opinion, knowing I don't have much right to do so:
MCCM's builds don't even run on my device, and Warren's ones work for 5 minutes then corrupt my SD! and yes that includes AmDroid.
it's not SD-related since I'm already using a build that's stable enough to handle 3 days of constant work on the same card.
Both of you guys are great in what they do really, considering the number of users you serve, but I don't think a public thread is the right place to argue. PMs were created for a reason, and there are MODs to complain to and stuff like that.
In my opinion, no matter who's right here, you both are looking bad.
HD2one
It is an older build, but very stable. I get 2970 on quadrant so it takes full advantage of the HD2's power. I've tried new builds, but i always come back.
Hey Guys,
I have been wondering why hasnt any dev(s) setup CI anywhere? I see tons of devs doing constant checkin and daily even hourly build on different roms however the end users are stuck with having to install SVN tools download the source compile and create a build? Cant we automate this process using continuous integration where we create a build script that upon each commit/checkin a build script is kicked off. Compiles the new rom zips/signs it and published it to a host somewhere that the end users (us) can just download? I am sure this would save a lot of headaches and time for everyone. Also at part of continuous integration you can also do things like setup build verfication sets (usually unit tests) to verify nothing was broken in the rom before a publish happens. This would also help to increase the quality and reduce bugs in each build.
Thoughts?
Nooooo don't post in Dev, you will be trolled. And yea nice idea btw.
Sent from my PG86100 using XDA App
Where the link at? Really wanna try it man
Sent from my super 3d running Viper RC1.3
while a nice idea .. but wrong section ..
Anyways back on topic. I think there is a script to do this burning don't think it would be as extreme as every commit. The problem is is that devs don't just make one commit at a time. It could be several in 1 min. If so it could overload the buildbot. Its better to keep it nightly to we can test more at one time and we make sure the devs make the edits they want.
Sent from my PG86100 using XDA App
clark44 said:
Off topic but really dude? I see you posting the same **** in every thread in the dev section that doesn't belong. Just because u have that recognized developer status doesn't mean u can go around ripping on users. I'm a dev to you don't see me trolling these threads. Don't reply to this just read it.
Anyways back on topic. I think there is a script to do this burning don't think it would be as extreme as every commit. The problem is is that devs don't just make one commit at a time. It could be several in 1 min. If so it could overload the buildbot. Its better to keep it nightly to we can test more at one time and we make sure the devs make the edits they want.
Sent from my PG86100 using XDA App
Click to expand...
Click to collapse
Appreciate the feedback Clark. I know for a fact you can configure each CI tool differently perhaps an hourly instead of commit based would be more ideal? The goal of my suggestion was really three fold. To reduce the bugs in each build, To implement unit tests in each build that could kick off to verify the build and functionality ensuring nothing got broken in the last series of commits and to get signed builds that are more stable out to the community faster. Rather than having to rely on the end user to figure out SVN. I notice there are tutorials on using SVN in here. Wouldnt that be in the wrong section too? What does that have to do with direct developing? SVN is merely version control? Anyways I believed my thread was directly target to development and all ROMs especially those that have team collaboration. I am sorry that if people dont agree and feel that I started this thread in the wrong forum. However I did want to make sure that it was visible to developers so that they would see it and possibly think it over as in the long wrong I believe it would make there lives easier. However I am sure the flaming will continue....
I think this is a horrible idea. If you don't have the ability to learn to checkout and export an svn repository, than you shouldn't be playing with an experimental nightly build. You see all the people who have issue's with STABLE builds because of stupid things like loading too many apps into memory? Imagine how many stupid questions would flood the nightly threads if there was an automated nightly build.
DeMiNe0 said:
I think this is a horrible idea. If you don't have the ability to learn to checkout and export an svn repository, than you shouldn't be playing with an experimental nightly build. You see all the people who have issue's with STABLE builds because of stupid things like loading too many apps into memory? Imagine how many stupid questions would flood the nightly threads if there was an automated nightly build.
Click to expand...
Click to collapse
This man knows what's up.
Hello People, I'm Moon And trough my world of android have i gotten lowend devices for own use. i love them because they're so cheap and still Great.
I have come from the GT540 Optimus to the ZTE blade and now the x8,
(I kept the Blade trough.) I am a big fan of Racht and his sense ports, what i want to ask you people for, since Racht seems to have disappeared should we do what developers and friends of him do. We finish what he started.
Most important is currently The GL Drivers I think, Maybe some RAM Management. The free ram is very low. (about 40\50mb) This causes Rosie to reload after coming from other apps. this would be cool to fix.
I asked XDA MEMBER # Kenia1234 (he ported it to the SGS)
About 3d\open gl and wifi. this was his reply.
however as regards 3D I fixed it using my device's libs under system/lib/egl or under /vendor/lib/egl and of course using a CM7 powered kernel...
as regards the wifi, it's a little bit more complicated...you'd need to have the bins of your device under /system/bin and the firmwares all in order, as the kernel wants to...
hope this was useful!!
Click to expand...
Click to collapse
Yes it was useful Thank you. any other Sense porters please contact us.
I know a little about this but not enough to do it myself yet.
Thank you in case of that you want to help.
~Updates~
XDA MEMBER # Paul1989 Is doing great work on http://forum.xda-developers.com/showthread.php?t=1294461
Click to expand...
Click to collapse
I haven't seen racht's new post since I join xda.
Does anyone know how's he doing?
kevinlogix said:
I haven't seen racht's new post since I join xda.
Does anyone know how's he doing?
Click to expand...
Click to collapse
I think he needs a little rest...
racht said that he will port HTC kernel and that means fully working Sense rom as soon as he's back.
I don't know where he is or what is he doing, but he's on xda often. (last activity today).
And I think he's getting Xperia Ray - his post here. Also that's the last thing he posted.
Anyway, the man will spoke, and we shoud donate to him a new device if he's selling his one. To continue development. But, we need to wait until the man spokes!!
I appreciate racht so much, and I hope he doesn't forget our X8.
OH.
Dare-Devil Inside said:
racht said that he will port HTC kernel and that means fully working Sense rom as soon as he's back.
I don't know where he is or what is he doing, but he's on xda often. (last activity today).
And I think he's getting Xperia Ray - his post here. Also that's the last thing he posted.
Anyway, the man will spoke, and we shoud donate to him a new device if he's selling his one. To continue development. But, we need to wait until the man spokes!!
Click to expand...
Click to collapse
I See, Thanks for Providing this information to the masses.
The Ray is the best Choice after the Arc, For me, Since i like big screens.
But yes. Lets just hope for the best. the Guy i updated on, (On the op) is doing GB sense too. We should let Racht Rest and hope for the best.
In racht's last Sense Port there is a lot of bugs. I really love that rom but it has a lot of bugs.
I was without SIM Card and in the Notification Bar it was showing that i used %S(something like this) tries for the unlock key and blablabla.
SD Safe to remove bug in ROOT Apps
I tried to connect the phone to my car radio and it doesn't show anything in the phone, only the icon changed to charging, but no led, no popup for connecting, nothing. And the radio does not recognized the phone. (i think it will happen the same in the computer, i think)
3d, wifi, 3G and vibra not working, as it shows on the original topic
So this is what has to be worked on
I cannot help you so much because i'm not a good java developer, i can only understand some parts of the code, but i cannot write it. But if you want a beta tester i'm here to try to find the maximum bugs i can
I will love if someone could continue what Racht did
I am following the news.
As I have said some months ago, X8 is now added to official CM tree, you can see here :
http://download.cyanogenmod.com/?device=shakira
So, I guess thats the end of CM story (even that I prefer tweaks by doixanh).
Sense rom depends on kernel features that do not work on .29 kernels.
See HTC threads, all new roms require .32 or .35 kernels, lets hope X8 will get a new kernel ported.
And thanks again for support
racht said:
I am following the news.
As I have said some months ago, X8 is now added to official CM tree, you can see here :
http://download.cyanogenmod.com/?device=shakira
So, I guess thats the end of CM story (even that I prefer tweaks by doixanh).
Sense rom depends on kernel features that do not work on .29 kernels.
See HTC threads, all new roms require .32 or .35 kernels, lets hope X8 will get a new kernel ported.
And thanks again for support
Click to expand...
Click to collapse
Great to see your alive Racht! And whut o:? does this mean that this rom is a fully working CM7 release like my Blade has?
And Yes, I've heard about the basics of porting sense.
Even trough you would be the best teacher.
Does this mean That Your Leaving the Shakira forums now racht?
wow! is this ROM stable knowing that it came from cyanogen?? please can someone confirm this? it doesn't have any details of its features included on it...
mikel_0004 said:
wow! is this ROM stable knowing that it came from cyanogen?? please can someone confirm this? it doesn't have any details of its features included on it...
Click to expand...
Click to collapse
Dude, thats the wrong topic. But look at the type or search for details of the features here at xda -.-
Paul1989 said:
sorry i have to abandon you all i am moving to HTC as i have swapped phones with my brother. i will NOT be carrying this project on and now i leave in the hands ov the other dev's on this forum. sorry to do this but ide rather have a HTC
Click to expand...
Click to collapse
As he wrote, he wouldn't be developing sense on X8. That's bad. Anyone want to take care of this project?
Blagus said that we have to port HTC kernel first, but it's .32 or newer kernel. We have only .29 now. Therefore it follows that we can't have sense on X8 now.
mikel_0004 said:
wow! is this ROM stable knowing that it came from cyanogen?? please can someone confirm this? it doesn't have any details of its features included on it...
Click to expand...
Click to collapse
is stable but not complete!
It´s just the FXP 030, AFAIK.
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.
As many of you might have noticed, I've been pushing lots of MiniCM sources the last days. ICS is done and JB is on its way.
I'd like to take this opportunity and invite other developers or members that would like to contribute patches to do so. We already have some people contributing code for MiniCM and I would like to see more joining in. The code is available at: https://github.com/MiniCM
Why do this now?
This arch is reaching its limit as far as android development is concerned and there is too much ROM fragmentation for an old phone like this.
I know that most of the ROMs around are already using MiniCM binaries or sources and I'm ok with that. However, now is the time to consider contributing back and helping this project.
MiniCM is a fork of CM dedicated for these old phones. Notice that we are never gonna have official CM support, this is actually the cause that MiniCM serves
Licensing
I decided to keep my modifications Apache licensed. This is what gave android such a rapid development and I'd say has proven successful so far
I'd like to see this thread being used for Development ideas and solutions. NOT by user spamming (which will get you banned soon anyway since this thread is mod-monitored - you've been warned).
Reserving for build instructions
I can try to do option for disable/enable display button, but i'm not sure that i can do it
Lets keep this thread clean and on topic, as the OP has requested
We (the mods) will have a close eye on things, so lets not have any nonsense :good:
AChep said:
I can try to do option for disable/enable display button, but i'm not sure that i can do it
Click to expand...
Click to collapse
You mean the navigation bar right?
See this: http://review.cyanogenmod.com/#/c/20726/
nobodyAtall said:
You mean the navigation bar right?
See this: http://review.cyanogenmod.com/#/c/20726/
Click to expand...
Click to collapse
Oooppss, hour of my time wasted Cyanogen guys are fast
FAQ of course
and remember, for each version (miniCM7,9 and 10) there is a dedicated FAQ
that you can find here
I have a little idea. Many users of X8 and X10 Mini/Mini Pro uses stock kernel and can't unlock bootloader. I tried to make an addon to boot MiniCM7 based ROM's on stock, but still without success. With your help, nobodyAtall and other users, we can make such addon. I'm too unexperienced yet to do this by myself. What are your thoughts?
eagleeyetom said:
I have a little idea. Many users of X8 and X10 Mini/Mini Pro uses stock kernel and can't unlock bootloader. I tried to make an addon to boot MiniCM7 based ROM's on stock, but still without success. With your help, nobodyAtall and other users, we can make such addon. I'm too unexperienced yet to do this by myself. What are your thoughts?
Click to expand...
Click to collapse
Hi eagleeyetom,
Unfortunately stock kernel is VERY outdated to be usable in modern ROMs (e.g. gingerbread onwards).
In essence, one would have to replace the kgsl system to get the graphics to work decently with latest adreno blobs. Also I'm not sure if usb would be working since this too is outdated.
Other things to note: RAM (175MB if I remember correctly) is desperately low for modern Android versions, performance would also not be good enough for daily use. Kernel-side, I'm doing my best to boost performance as much as possible by backporting almost all of the main components that android uses from later versions.
All in all, for gingerbread it would be possible with serious performance sacrifices which I'm not willing to accept (even as a user). For ICS/JB, just forget it.
Perhaps a good project would be to make bootloader unlocking work for recent devices...
I understand your concerns and also think that stock is utter piece of crap, but it's still worth a shot. Such universal patch would improve development to our old shakiras. Your MiniCM is way better than official CM - really great job. Even with these bugs you've mention it's better than spent cash to unlock bootloader. I really admire the work of Alf and you - it's amazing to have such modern kernels to over-two-years-old devices.
Worse performance is a fact, but the ability to use almost every CM7 ROM on stock is tempting. This would be a great contribution to our small community.
P.S. I also think that you should have Elite Recognized Developer title. Such good work should be appreciated.
eagleeyetom said:
I understand your concerns and also think that stock is utter piece of crap, but it's still worth a shot. Such universal patch would improve development to our old shakiras. Your MiniCM is way better than official CM - really great job. Even with these bugs you've mention it's better than spent cash to unlock bootloader. I really admire the work of Alf and you - it's amazing to have such modern kernels to over-two-years-old devices.
Worse performance is a fact, but the ability to use almost every CM7 ROM on stock is tempting. This would be a great contribution to our small community.
P.S. I also think that you should have Elite Recognized Developer title. Such good work should be appreciated.
Click to expand...
Click to collapse
I see what you mean. Gingerbread compatibility is feasible BUT is gonna be pretty slow - in fact REALLY slow compared to MiniCM7.
We try to give a top quality ROM, so if this would ever happen it would be like a flashable zip and totally unsupported
I hope a lot pf devs will join the development. Cause everybody is working alone and if you all work together, it will bbe better for you and all ROM users. You'll develop quicker and easier.
Envoyé depuis mon Sekiz avec Tapatalk
nAa, is there a chance we can have CWM 6.XX on our GB kernels ?
RohinZaraki said:
nAa, is there a chance we can have CWM 6.XX on our GB kernels ?
Click to expand...
Click to collapse
I think it is possible, you can try it yourself, because you are able to change the recovery of the Kernel
actually it's possible. you just need to change the recovery file in the ramdisk with the one from JBMiniProject kernel or with one you compiled.
Why do not use the "Camera ICS+" in the market to replace the default camera app instead of taking a lot of time to fix the camera ???
LEDelete said:
Why do not use the "Camera ICS+" in the market to replace the default camera app instead of taking a lot of time to fix the camera ???
Click to expand...
Click to collapse
nAa roms are pure CM roms custom built for our device. If you see there is no third party apps. Not in GB and ICS and neither in JB.
RohinZaraki said:
nAa, is there a chance we can have CWM 6.XX on our GB kernels ?
Click to expand...
Click to collapse
I was trying something similar last night but with FroyoPro25.. Trying to get usb tethering working in it..
Can you all focus on GB please?
Working on ICS and JB is useless because they will never work smoothly on these old phones
shvelo said:
Can you all focus on GB please?
Working on ICS and JB is useless because they will never work smoothly on these old phones
Click to expand...
Click to collapse
And what has left on GB to be developed? How can we improve it?
Sent from my X8 using xda app-developers app