yashsingh1/xdaforums huggingface dataset:
[Touch Pro, Fuze Android Development] detule:
I am attaching the *dat (renamed to *.txt) that made it through the mailing list this morning - it does not contain a patch only a git-status snapshot of your local tree. Please follow the instructions in the "Submitting Patches" page quoted above, if you need help come around on #xdandroid again. Once you have properly formatted patch, post it to the mailing list again.

Nobody is singling you out, every patch goes through the same peer review process. It is the only way an open source project with multiple contributors can be maintained.
[Touch Pro, Fuze Android Development] arrrghhh:
Thanks Detule.

Brinka123 - honestly... No one is singling you out. We're not trying to be mean... this is how open source works. If you want something fixed - it's best to fix it yourself. Then once you have it fixed, it is an annoying process to get it submitted properly. I'll admit it. BUT - it's a required step. First, git formatted patches make it simple for the maintainer to take your patch and implement it. If it isn't properly formatted, the maintainer would have to modify it, and then giving you proper credit in the tree isn't possible. Plus, it makes more work for the maintainer.

I hope you understand... again, no one is trying to do this to be mean to you. This is just the process you have to go through... We try to document it thoroughly to encourage people to submit patches! Thanks!
[Touch Pro, Fuze Android Development] littlebigtux:
Loosing this kind of pearl for technical reason would be ridiculous.

If the process is to complex

You should go to 4shared.com (free) and upload the modified files then attach a link in your next reply here.

Or attach them directly in your reply on this forum (depending of their weight.)

Hope talking other sites is not out of rules....
[Touch Pro, Fuze Android Development] arrrghhh:
Uh... what?

He's already attached the compiled kernel - which we know works. We now need to review the actual code, which should not be uploaded to some file sharing site. That can be attached here as well but...

If he just wants to post a patch and wants no credit for it, one of our devs can modify the patch and get it implemented. But then no credit will go to Brinka123 - and he did the dirty work, he should get the credit! You cannot get proper credit unless you submit a git-formatted patch as per the Submitting Patches page.
[Touch Pro, Fuze Android Development] littlebigtux:
In another post Brinka said:

I was suggesting a "raw" upload of the 4 files he modified before compilation, because Wifi doesn't work in the final kernell he posted
[Touch Pro, Fuze Android Development] arrrghhh:
That's fine, unless they're gigantor he can zip them up and attach them here...

However, I want to make it perfectly clear - if he doesn't properly git format a patch, he will not get credit for the patch!!

Hence why other devs don't really like doing that - they don't want to steal credit from whoever actually made the patch.

There's a method to the madness. It's not an accident... If brinka123 wants to upload the changed files here, that's fine - but I would still encourage him to git format the patch and submit it as such once he has that figured out. Git is used in a lot of open-source projects, so it's not a bad idea to learn in general.

Thanks!
[Touch Pro, Fuze Android Development] brinka123:
Here I agree with arrrghhh, there must be a standard process how changes are submitted and integrated by a team. This is the way to go and to keep a working kernel. Only want to say that the process it self is not clear and open.

After (again) one hour searching how git works. I wanted to check whether I am realy at the latest branch: I am: I checked with "git branch" and "git log".

I am on htc-msm-2.6.27 last commit from me and then Fri 19 Aug from mweirauch. The last one is commited in the 148 kernel !!

So this shows that my code is the same but the compilation is different.

I only need to know how you do your things....

Sorry I am bothering you all but I never worked with linux before and all those tools. But since the end of the 80's nothing changed...

Since a few weeks a managed to install vmware,linux umbuntu,toolchain, cloned linux-msm, compiled it, created a kernel (modules and zimage), debugged it, now the last step get the change back to be able to put it on the TP2 of my daugther. From her I get the real credit...:)

@arrrghhh did your received the (simple) change now?

And thank you all..
[Touch Pro, Fuze Android Development] detule:
While you seem to be on the correct branch, the last commit I see is Wed Sept 14 from [acl]. You can view the commits here: http://gitorious.org/linux-on-qualcomm-s-msm/linux-msm/commits/htc-msm-2.6.27

Make sure you do a git pull to merge the latest commits.

This link has a good summary on how to build the kernel, and even provides a helpful script for bundling the modules:

http://www.facebook.com/topic.php?uid=394317262428&topic=14012

Rather than using the toolchain found on that page I would use 2010q3 (it hasn't failed me to date). You can find it here:

https://sourcery.mentor.com/sgpp/li...-none-linux-gnueabi-i686-pc-linux-gnu.tar.bz2

---------- Post added at 05:54 PM ---------- Previous post was at 05:49 PM ----------

Also, wi-fi isn't working with the kernel+modules you attached to an earlier post because "modules-andre.tar.gz" is not a proper naming convention for the module tar balls. There might be something else broken with your modules, but as it is, those modules are not even getting unpacked by the xdandroid init script when Android boots. Parsing through the build script in my previous post should help set you up with means to properly build/name the modules.

Though, for now all is needed is for you to submit a proper patch (not necessarily build the kernel and modules). This involves cloning the htc-msm-2.6.27 branch, making your changes, commiting your changes in your local tree, and then format a proper patch.
[Touch Pro, Fuze Android Development] brinka123:
Thanks for your tips.

I followed the procedure as decribed on the wiki, 2 nights ago. So according to me I did this already.

In my local tree I see a commit with the files I changed, and I sent (again this morning) a mail to the mailing list with an attachment (.dat file), I can see its on the mailing list with my commit text.

So I am done... (according to me :rolleyes:).

---------- Post added at 08:47 PM ---------- Previous post was at 08:26 PM ----------

I read your reference to how to build a kernel.

Not much new, only I didn't do the git clone from compcache.

On the IRC of XDANDROID I asked that I missed some modules after generation.

Guys from XANDROID told me to get it somewhere, so I pulled them from the

current kernel.

Now I understand why Wifi doesn't work, I am missing something in de zImage.

According to me modules-andre file loads only with the attached haret, because it is to big. (also heard from the IRC).

But question to you is, is your build outcome exacly the same as a published kernel ?? Probably not.
[Touch Pro, Fuze Android Development] detule:
Did you read my post here? If that's the ML post you speak of, then the attachment did not contain a patch, or any code whatsoever. Perhaps I am wrong, and you are referring to a different ML posting that I have not received, in which case I am sorry for spamming the thread.

If you are still experiencing issues with formatting a patch, this may be best resolved if you show up on #xdandroid where you can communicate in a more immediate fashion with either me or one of the other folks over there that have experience with building the kernel/working with git.
[Touch Pro, Fuze Android Development] brinka123:
Now I got realy mad!!!!!!

Last sentence of the patch procedure "Submit your patch to the developers' mailing list at xdandroid-dev@lists.xdandroid.com and the appropriate maintainer will review it. If the patch is acceptable as-is, the maintainer may commit it without contacting the author first. If further development is necessary, the maintainer (or another team member) will contact the author with advice on what must be done.

So contact me and tell me how to submit a patch using the mailing list.

This is also what I asked 2 nights (nearly 3) nights ago!!!

And put it on the wiki page!!!!
[Touch Pro, Fuze Android Development] detule:
No need to get upset - everyone here is trying to be reasonable. The misunderstanding stems from the fact that you have not in fact submitted a patch to the mailing list, as of yet. I am not a member of the xdandroid development team, nor do I have a RHOD100 so I have absolutely no vested interest in this patch, yet here I am trying to help you out - so keep your cool.

The instructions for submitting patches that have been shown up in the last few posts are fairly clear IMO, and I (and others) have followed these without problems. I can see however, how seeing git for the first time can make it seem convoluted. If you need some help with git, come around on #xdandroid (if you PM me we could try and setup a time when we're both online).
[Touch Pro, Fuze Android Development] brinka123:
maybe I have to talk in #XDANDROID style:

>dno

>nthng from dev's

>fllwd wiki

I hope my point is clear. Now its your turn xdandroid.
[Touch Pro, Fuze Android Development] arrrghhh:
Excuse me?

None of us have interacted with you in this manner. At least I haven't, and from what I've read in this thread, no one else has either.

I also don't have a RHOD100, and also do not have a personal interest in your patch. If you're going to act like a child, why should we help you?

We've provided all the answers you could possibly want. Perhaps there's not a good wiki page on compiling the kernel, HOWEVER, there is a great wiki page on submitting patches. So there's no excuses, and I don't know why you're acting so ungrateful. You should know more than anyone how hard a project of this magnitude is to manage, and we're doing this in our free time. No one is getting paid to do this, or to put up with you. Please, be more considerate.

Edit - Either post your patch, or pull your compiled kernel. I am done with your attitude.
[Touch Pro, Fuze Android Development] littlebigtux:
:eek: Wow!!! :confused:

Brinka123 exploded in flight or what!?!?!?

Not enough sleep, maybe?

What a mess! :(
[Touch Pro, Fuze Android Development] brinka123:
I am pretty serious, the XDA wiki also the patch part is not clear enough.

It took me so much time to figure out how you guys work.

So pleeeeeeeeeeeeaaaaaaaaase update the wiki, not only for me but for others too.

I am still searching how to create a file of the patch which can I attach to the mail to the mailing list. Thanks for helping me out using #xdandroid but this is nothing for me. I need to find things.

On this wiki

http://ariejan.net/2009/10/26/how-to-create-and-apply-a-patch-with-git/

I found:

git format-patch master --stdout > nameofpatch.patch

So the .patch file needs to be attached to the mail to the mailing list??

When yes, pleeeeeeeeaaaaaaaaase add this to the wiki, it is not clear where and how a patch file is created.

And pleeeeeeeeeeeeaaaaaase reply to the mail i send to the mailing list so I know whether a patch is OK, Processed or Rejected or something like that.

Sorry guys, but I nearly threw my computer out of the window yesterday. Took me one day to recover from this madness...
[Touch Pro, Fuze Android Development] arrrghhh:
I don't know why you're getting so angry. No one is being hostile to you...

http://xdandroid.com/wiki/Submitting_Patches <--- does that not cover submitting the patch for you? I'm confused.

I will agree, the wiki needs a page on building the kernel. But I'm unsure as to what you mean adding stuff to the submitting patches wiki. What is missing there?

Creating a Formatted Patch - should cover all the git work needed to get the actual patch. Then once you have the patch, send it to the mailing list.

I will let you know as soon as we have a good patch from you. So far, I have not seen the actual code. Thanks.
[Touch Pro, Fuze Android Development] Enigmatik_best:
To Brinka123, arrrghhh, detule, viruscrazy, littlebigtux and others who contribute to the project of fixe the cam on Rodhium devices

Pleaseeeeeeeeee don't stop the project of fixe the cam for all Rodhium (specialy the Rodh100 who seem to bug more than others)!!!

Do not stop the project only because of a misunderstanding and too little sleep please :rolleyes:

If everyone puts on the good will, you should get to hear you and solve this problem of communication and sending the correct file to Xandroid wiki.

I agree with Brinka123 the FAQ Wiki Xandroid is not clear at all and should be at least as developed as the link Brinka123 found: http://ariejan.net/2009/10/26/how-to-create-and-apply-a-patch-with-git/

But do not be offended this FAQ incomplete for now, just try to find a way to send this "****" file for now ... you can discuss the faq later :)

Please, for all of us who wait this great solution of cam fixe :o

PS: Which of these files I need to change for this to work without losing my data and my current setup?

Camera100.ZIP =

- haret.exe

- modules-andre.tar.gz

- zImage

(- Startup.txt) i know that i can keep mine.

And can i change the name of "modules-andre.tar.gz" to something like "modules-2.6.27.46-01348-g9de837f.tar.gz" for this to work as Detule pointed out in his message?
[Touch Pro, Fuze Android Development] arrrghhh:
The project isn't stopping by any means. Just trying to get this patch committed to mainline... If you haven't done open source development before, it can be odd. We definitely need to flesh out the wiki - there's no page on how to build/compile the kernel. However, I don't see how the submitting patches page can be improved. It has all the steps required, from what I can tell...

Edit - as for your other question I have no idea what you're talking about, sorry.
[Touch Pro, Fuze Android Development] brinka123:
Finally I discovered that a <name>.patch file is generated, by git format-patch.

It was there 3 days ago already....

Posted on the maillist.

Don't think the wiki will be changed, it would have been a great help.
[Touch Pro, Fuze Android Development] arrrghhh:
The wiki can be changed.... but I don't see how it needs to be changed.

It appears the patch is valid. Thank you brinka123, it should make the mainline kernel soon. Again, thanks for your efforts... sorry for the complexity... please let me (or another dev team member) know how we can improve. I will be making a kernel compiling wiki page soon. Thanks once more...
[Touch Pro, Fuze Android Development] Enigmatik_best:
Test = good! :cool:

I succeeded in creating an additional folder with FRX07.1 especially devoted in test (besides my FRX07.1 in root of my card SD) (thanks to "Arrrghhh" for the precious advice). I changed the startup.txt for the launching of XDAndroid since a sub-folder.

Then, I simply replaced the file "modules-2.6.27.46-01348-g9de837f.tar.gz" by that of Brinka123: "modules-andre.tar.gz".

And does it work ... Wifi included!

The camera works as much for the photos as videos (a bit slow but it is normal for a smartphone with only 288Mb RAM and a processor 528 Mhz (HTP2 Rodh100_FR) :D

Tested on native camera program and "Camera360". Had a freeze with "Camera Advance Lite" but i think i was out of RAM memory. I'll doing more test later.

I wait the end release of Kernel to put it in my principal XDAndroid.

Good job! Thanks! :)

Tips: Don't replace the original Haret.exe by the one of Brinka123, that's don't work (i think it's the Haret.exe only for the devices that Brinka have).

I didn't try to replace the zimage because that work without and I do not know for what it serves.

To keep your data, setup and touchscreen calibration, save data.img and ts-calibration files (you don't need to erase/replace these but doing a backup is safer).
[Touch Pro, Fuze Android Development] Stijnjits:
Is this nice patch going to make it into the autobuild? Or is there someone who can build a kernel with working wifi etc with this one?
[Touch Pro, Fuze Android Development] helicopter88:
It's going to come soon,it just need a few things to be changed to avoid not breaking other devices's things..
[Touch Pro, Fuze Android Development] brinka123:
Hi Guys,

Today i managed to generate a kernel with wifi and camera working for the 100.

Attached the kernel. It also will not start using a normal haret, so I attached the haret and the changed startup txt for the 100. Still looking for the right toolchain...

I am not completely happy with my solution because in dark cirumstaces the camera hangs. But I have a good starting point to go on now.

In normal light conditions its no problem.

The xdandroid dev are working on a solution so the risk to other devices

which use the mt9t013 (raphael, sapphire, diamond and halibut) wil not degraded. I changed 2 register parameters to change the frames per second. So when raphael or sapphire owners are willing to test my kernel (change the startup.txt!) the integration risk of this patch in the final solution is reduced...
[Touch Pro, Fuze Android Development] Enigmatik_best:
(see first my Edit 2 then my Edit 1 in the end of this post; and then the entire post ;)

Finaly it's work (just had a problem with launching first native camera application and then "Camera360" but when I try first the "Camera360", it's seem to work). Must to do differents test to see if the native cam apk and the Camera360 apk can work both in the same boot.

Sorry to have writed it in several steps but it may help others to follow the right path and not to make the mistakes that I have comise. It can also help you to answer my question on the 'zImage' file and see why your file Haret.exe does not work for me.

If you could also respond to my question about additional rows that you have in your file 'startup.exe' please :o )

First try and first failure

Doesn't boot when i click on the HaRet.EXE (for the first time after copying your files).

I continue searching where is the error in my procedure. It worked with your first patch / kernel. I have of miss something.

I did that:

Replace these files:

- haret.exe (also tried with the "normal" (origin file) Haret.exe = no result)

- modules-2.6.27.46-01349-gb602130-dirty.tar.gz

- zImage

I kept my file 'startup.txt' and have not tried erasing my file 'data.img' (and then put it back if it works).

My file 'startup.txt' contains the following lines (in red, the differences with yours):

Mine is:

Yours is:

When testing your first patch/kernel, I have replaced only the file "modules-2. 6. 27 46-01349-gb602130 - dirty .tar .gz" and therefore have not replaced my "HaRET.EXE" or "zImage" (and I also kept my "Startup.txt" with only modified, the path to my Android test subfolder).

Do you know what error/missing I did?

Second try and first half-win

:rolleyes: :)

Edit 1:

I tried with mine "zImage" file and it's work :) (Result: I finaly only change the module file (1))

Native Camera application is ok (video too :) ) but hangs/freeze with "Camera360" application. Native Camera is very bad quality and function so I hope "Camera360" will work in the future without freeze :rolleyes:

I must to continue my tests to be sure. But it's realy in good way :cool:

Third try and almost entire win

;) :p

Edit 2

: Finaly, "Camera360" application seem to work (I reboot my device and launch "Camera360" first and not after tried native camera application).

I must now to test again when I launch first the native camera application but seem to go in the good way :o

Thanks very much for your job and keep on working in this way ;)

(1) I don't know the exact role/feature of the 'zImage' (I just know it's an important part of the Kernel and that the Kernel is the core of the system)

Do you think I need your "zImage" or I can keep mine (the one of the origin FRX07.1)? And if I need yours, I notify you that he doesn't work with my phone for this moment. Perhaps you need to adapt it (?).

(2) Do I need your line set initrd_offset 0x00a00000 in my Startup.txt?

And do i need the the parameter force_cdma=0 in my Startup.txt?
[Touch Pro, Fuze Android Development] littlebigtux:
HALLELUJAH GOD!!!!

.....Hu...I mean, thank you for this work Sir Brinka....

On my Rhod 100_fr there'no hang at all.
[Touch Pro, Fuze Android Development] brinka123:
Thanks for testing/experimenting enigmatic_best.

1] The attached modules won't load with my haret included in the tiadroid build.

They are loaded with the haret from the first post of this thread.

Is is possible that you use this one already??? Where is your haret coming from??

2] I don't understand why in your experiment the changes work by replacing the modules only.

What I now is that the cameradriver is included in the modules and zImage.

These 2 are always build and deliverd as the kernel.

3] CDMA=0 is something for the TIADROID build probably can be removed in your sitation.

I still hope the change will be included in a "real" kernel..... Depends on testing on saphire e.tc..
[Touch Pro, Fuze Android Development] Enigmatik_best:
Thanks for your answer :)

1) My Haret.exe is that of origin from the build "FRX07.1" of Arrrghhh and her team: http://xdaforums.com/showpost.php?p=15692363&postcount=1

I did not try with the Haret.exe of the first post of this thread because it is old and i think out of date.

2) I would like to try with your zImage but that does not work. When I click Haret.exe, it freeze at the beginning (at the exit of WinMo 6.5. The logo of the Linux penguin, does not even appear). :confused:

3) ok for the CDMA line in the startup.txt. And what about your line "set initrd_offset 0x00a00000". For what it serves and is she useful to fix the bugs of the camera :confused:

If I understand well, the good drivers for the camera are in the module AND in the zImage. So, your zImage is essential for the proper functioning of the camera. It's that?

Thanks for your help :o

PS: the camera still freeze randomly and in a little times, I can wait a little and the application close but the main panel is only in landscape mode. In this fact, only the Home button (the fourth) still works but the other 3 buttons: Call, menu, back (first 3) no longer work :(

That said, I do not despair because the photo-camera is already longer without blocking and the video-camera works (never worked before your patch) :D :cool:
[Touch Pro, Fuze Android Development] arrrghhh:
1. You probably need that other HaRET in order for it to work. Not the HaRET that is included in FRX07.1, but the one on brinka123's post.

2. See #1.

3. This is required if the kernel goes over a certain size. This value needs to be increased, in order to give the kernel more room to breathe.

4. If you're not using his zImage, then you're getting no benefits of his patch. His patch is in the zImage - that's the kernel. You're literally doing nothing different with the cam if you're not using this file. The only other thing you could change is the modules, and those are only for additional modules like wifi. Again, nothing to do with cam. If you're not using his zImage, you're not using his code!!
[Touch Pro, Fuze Android Development] Enigmatik_best:
Thanks very much! It's work with the zImage of Brinka123 now!!! :D :cool:

I added the line set initrd_offset 0x00a00000 in my startup.txt and remove the overclocking line.

Congratz! :)

I tried the Haret.exe of the first post of this thread and then I tried the Haret.exe of Brinka123 ... all both work! :)

I can test with the Haret.exe of FRX07.1 and see the impact.

I dunno the difference between the 3 Haret.exe? Can you say me witch is?

Then i'll test with overclocking if it work.

Thanks Arrrghhh for your informations, I know better now the different parts and features of a build :)

I'll let you know my result :)
[Touch Pro, Fuze Android Development] arrrghhh:
I'd have to do a comparison, but I'm betting the HaRET on the first post of this thread and brinka123's is the same. The HaRET included in FRX07.1 bundle is a little bit older and doesn't like to boot kernels once they get too big. I'm no expert on the nitty-gritty details here... I kinda understand the init_offset, but I'm not sure on "why" the new HaRET is needed... but it is ;).