Database Users

Droid has been rooted!

I know. This is the hero forum. But if anyone has a droid or knows someone with one maybe we can get a dump?

Forgot to, post the link
Http://alldroid.org/viewtopic.php?f=210&t=567

awesome! i'd expect you goons to have vanilla 2.0 ready for the mass sprint crowd by tomorrow right? lol isn't a dump all we'd need? pardon for my ignorance but what changes would be made to be compatible to the cdma hero?

Excellent! Now we just need a full rom dump (not just the /system folder which is all that's available right now).

flipzmode said:
Excellent! Now we just need a full rom dump (not just the /system folder which is all that's available right now).
Click to expand...
Click to collapse
+1
I could use those apk's to build a "fuller" AOSP... that is assuming data can be made to work.

Thats what I'm hoping for. So please everyone who has access to a droif, root it and get a dump for us. Please

I was excited for droid users to find out it had been rooted. Now I am really excited because I didn't even think of the benefits it would bring to us!

flipzmode said:
Excellent! Now we just need a full rom dump (not just the /system folder which is all that's available right now).
Click to expand...
Click to collapse
Request made @ AllDroid
http://alldroid.org/viewtopic.php?f=210&t=570

WhiteWidows said:
Request made @ AllDroid
http://alldroid.org/viewtopic.php?f=210&t=570
Click to expand...
Click to collapse
Sweet. Post back here if they provide it please. I can only watch so many forums. heh.

So let me get this straight, a full dump from the Droid will help us get 2.0? If so AWESOME! I have a friend who has one, I'm sure he'll be rooting tonight I can get a dump tomorrow if you don't get one sooner.

NCX001 said:
So let me get this straight, a full dump from the Droid will help us get 2.0? If so AWESOME! I have a friend who has one, I'm sure he'll be rooting tonight I can get a dump tomorrow if you don't get one sooner.
Click to expand...
Click to collapse
It's more of a theory than anything. But if we can get their rom booting on our phone then we have a much better chance of getting things working rather than the gsm version we've been hacking up to try and work.
If anyone has access to a rooted droid then let me know. Although it will be much better once they have access to nandroid because pulling these files while the phone is booted up doesn't always work.

flipzmode said:
It's more of a theory than anything. But if we can get their rom booting on our phone then we have a much better chance of getting things working rather than the gsm version we've been hacking up to try and work.
If anyone has access to a rooted droid then let me know. Although it will be much better once they have access to nandroid because pulling these files while the phone is booted up doesn't always work.
Click to expand...
Click to collapse
I don't think that's true.. our kernel/drivers are way different than theirs.. we will be about the exact same point that we are now, and there are full rips out of the droid now on alldroid.org

nelson8403 said:
I don't think that's true.. our kernel/drivers are way different than theirs.. we will be about the exact same point that we are now, and there are full rips out of the droid now on alldroid.org
Click to expand...
Click to collapse
I agree but it's a lot easier to make a trackball work, to make leds work, and to make wifi work rather than trying to make it work on a radio that it wasn't designed for.
The image that the guy posted on alldroid is corrupted. It won't unyaffs. And based on the file size I would say it's just a system dump anyways.
Thanks to whitewidow I was able to get my hands on the boot.img by copying it off of /dev/mtd. The build went smoothly however it reboots instantly after the HTC logo. It is never recognized by the debugger. So this is either caused by corruption from how we obtained the boot.img, or the architecture / processor are just too different to work on ours at all. I am not the type that can build kernels from scratch though so maybe someone out there better than me will get it soon.

flipzmode said:
I agree but it's a lot easier to make a trackball work, to make leds work, and to make wifi work rather than trying to make it work on a radio that it wasn't designed for.
The image that the guy posted on alldroid is corrupted. It won't unyaffs. And based on the file size I would say it's just a system dump anyways.
Thanks to whitewidow I was able to get my hands on the boot.img by copying it off of /dev/mtd. The build went smoothly however it reboots instantly after the HTC logo. It is never recognized by the debugger. So this is either caused by corruption from how we obtained the boot.img, or the architecture / processor are just too different to work on ours at all. I am not the type that can build kernels from scratch though so maybe someone out there better than me will get it soon.
Click to expand...
Click to collapse
I'm pretty sure stuff compiled for the OMAP arch. Droid is not going to work in our Qualcomm arch. Heroes. I tried using "chat-ril" executable from Droid on my Hero and that doesn't work at all. OMAP and MSM have their own kernel trees as well, so their kernel probably won't boot on the Hero.

It's OMAP alright.
You wont get any of the normal binaries to run.
You can however grab some apks from it.
There is a dump out already btw, has been for almost a month now.

There has been a system dump yes but we are talking about a full dump including the boot.img file.

Boot image contains nothing useful for our purposes.
If you absolutely have to have the boot image someone posted it over on alldroid.org.

is it possible to get the new lockscreen from newly updated droid as verizon has spreaded 2.01 update for droid? cheers

G2 rooted, next myTouch4g???

http://forum.xda-developers.com/showthread.php?t=803208&page=39

I think that once their root method uss finally released we will be able to use it in the htc glacier
Sent from mai HTC AntiTitanic

Root Guide:
http://forum.xda-developers.com/showthread.php?p=9109921
So who's gonna do it first? You can always claim stupidity and bring it back to t-mobile for a replacement. Personally, I can't afford the downtime because I'm on call. :-/

If no one tries it by tomorrow I will do it. At work right now and have the kids tonight.

InGeNeTiCs said:
Root Guide:
http://forum.xda-developers.com/showthread.php?p=9109921
So who's gonna do it first? You can always claim stupidity and bring it back to t-mobile for a replacement. Personally, I can't afford the downtime because I'm on call. :-/
Click to expand...
Click to collapse
I would suggest not tryin to perm root until we have specific directions for our phone. It won't be too long until that happens so just be patient.

Good news and great work to the G2 team. Shouldn't take too long for us!

I am not 100% sure about this but we may need the kernel source for this. If I understand they way they got WP off was by using a kernel module to power down the emmc and then another to reinitialize it, we could need espresso source to make it work. I may be wrong though and someone may have it done by tomorrow.......

i'll wait for a script to be released to the market

double post

Don't try this with the G2 method. They're loading a kernel module that's kernel specific if I'm not mistaken. We need a specific module for the MT4G.
Sent from my HTC Glacier using XDA App

They did a awesome job!! Now everyone with the MT4G needs to bug HTC for the Kernel source code for our phones! Then we can recompile this the day its released and have S-Off on the MT4G. This will also let us create the overclock module for non rooted people. I cannot wait to see what this phone can really do!
Thanks to everyone in #G2root!!

Alright, I developed the effit attitude and figured if I screwed it up I would just play stupid. (I'm from Kentucky so the stereotype and accent work in my favor sometimes. )
I tried both kernel modules (wpthis-pre-ota.ko and wpthis-ota.ko) and both gave me an EXEC FORMAT ERROR. I ignored the errors and drove on with the instructions. DD'ing the hboot-eng.img went flawlessly and sync appeared to work b/c it just gave me a prompt waiting for the next command.
After reboot everything stayed the same S=on was still laughing at me. Sooooo, nogo.
All I got from this was the errors. No brick!

Gr8gorilla said:
I am not 100% sure about this but we may need the kernel source for this. If I understand they way they got WP off was by using a kernel module to power down the emmc and then another to reinitialize it, we could need espresso source to make it work. I may be wrong though and someone may have it done by tomorrow.......
Click to expand...
Click to collapse
I read a post saying they reversed engineered it before HTC released the kernel source. One way or another we'll get it.

grankin01 said:
Alright, I developed the effit attitude and figured if I screwed it up I would just play stupid. (I'm from Kentucky so the stereotype and accent work in my favor sometimes. )
I tried both kernel modules (wpthis-pre-ota.ko and wpthis-ota.ko) and both gave me an EXEC FORMAT ERROR. I ignored the errors and drove on with the instructions. DD'ing the hboot-eng.img went flawlessly and sync appeared to work b/c it just gave me a prompt waiting for the next command.
After reboot everything stayed the same S=on was still laughing at me. Sooooo, nogo.
All I got from this was the errors. No brick!
Click to expand...
Click to collapse
The EXEC FORMAT ERROR was because of mismatching kernel versions! We have to have one made against the HTC Glacier(MyTouch 4G) kernel source, which has not been released by HTC.
Also, the Engineering HBoot is specific to the G2. You could've bricked if you weren't careful.

travisjames said:
The EXEC FORMAT ERROR was because of mismatching kernel versions! We have to have one made against the HTC Glacier(MyTouch 4G) kernel source, which has not been released by HTC.
Also, the Engineering HBoot is specific to the G2. You could've bricked if you weren't careful.
Click to expand...
Click to collapse
Just figured I'd give it a shot. Nothing ventured nothing gained right.
Anyway, I figured it wouldn't work before I tried it due to different kernel builds. If I am looking at the two phones correctly they both have 2.6.32 kernels just different builds of it. And the architecture of the phones should be very similar based on the use of the qualcomm chips.
Could have bricked the phone, yes, but also could have (slight chance) worked without having to recompile anything.

grankin01 said:
Just figured I'd give it a shot. Nothing ventured nothing gained right.
Anyway, I figured it wouldn't work before I tried it due to different kernel builds. If I am looking at the two phones correctly they both have 2.6.32 kernels just different builds of it. And the architecture of the phones should be very similar based on the use of the qualcomm chips.
Could have bricked the phone, yes, but also could have (slight chance) worked without having to recompile anything.
Click to expand...
Click to collapse
attaboy

grankin01 said:
Just figured I'd give it a shot. Nothing ventured nothing gained right.
Anyway, I figured it wouldn't work before I tried it due to different kernel builds. If I am looking at the two phones correctly they both have 2.6.32 kernels just different builds of it. And the architecture of the phones should be very similar based on the use of the qualcomm chips.
Could have bricked the phone, yes, but also could have (slight chance) worked without having to recompile anything.
Click to expand...
Click to collapse
For sure. Someone has to be the first try it. Thanks for being the guy to put your balls together and do it.

InGeNeTiCs said:
attaboy
Click to expand...
Click to collapse
dwilson88 said:
For sure. Someone has to be the first try it. Thanks for being the guy to put your balls together and do it.
Click to expand...
Click to collapse
LOL, no prob! Just as eager for root and some cyanogen love (among other things) as anyone else.

Question: The desire HD is a different kernel correct?

grankin01 said:
LOL, no prob! Just as eager for root and some cyanogen love (among other things) as anyone else.
Click to expand...
Click to collapse
Haha...I'd settle for the battery percentage mod. I can't understand why this isn't standard....ugh

Making a Gingerbread NAND ROM for HD2

Ok, I'm loving Gingerbread, but m-deejay has been including Cyanogenmod in his recent builds, which I don't want.
I'm REALLY keen to work on my own Gingerbread build...but need pointers on the steps I need to take.
I want to use a clean custom Nexus One Gingerbread build, such as http://forum.xda-developers.com/showthread.php?t=885784
Then I'll have to replace the Nexus drivers and stuff with the HD2 ones...this is where the problem starts...how do I know which files are needed for HD2 specifically?
And then I need to add/remove apps etc to customise it?
I don't want anyone to hold my hand, just to at least point me in the right direction, as finding this information seems to be very difficult, unlike Windows Mobile cooking, which has lots of good tutorials...even though I'd expect that to be the other way around
I taught myself WM cooking & dev, but this is a whole new ballgame to me....
Appreciate any help I can get...
I'll happily donate a few $ to anyone who can help me get a stock build going...

No one able to shed ANY light? Give me ANY pointers?
Like I said, I'm willing to donate $ if I get help to get a ROM built...

Good pointers!!!
Have you tried with this tutorial?
SEE THIS!!!
This is the best step by step guide, and there is everything you need to port/make good working ROM for LEO.
Regards.

NemanjaLO said:
Have you tried with this tutorial?
SEE THIS!!!
This is the best step by step guide, and there is everything you need to port/make good working ROM for LEO.
Regards.
Click to expand...
Click to collapse
Yea I saw that, thanks...only problem is that it's an old build, and it's miui.
Where do I find the latest drivers etc? And how is a NAND build different? How do I package up a NAND ROM?

I was thinking the very same thing but when I started looking into it I got put off by the complexity and the time it would take.
Have you thought about just modding MDj's ROM, stripping it back to bare ginger and replacing the bits we dont want, this might be easier that building one from scratch.

Yea, it's a possibility...but I won't learn as much doing it that way...and I'd rather try to create my own than use someone else's hard work as a base, if you know what I mean.
I have time, and am willing to learn as much as I need to...I just need some pointers...there are plenty Android HD2 chefs now, surely one of them is willing to help out

It's really not that difficult. I didn't really like the CM mod either, so created my own stock rom. I'm now at the point where I got it all working. I don't mind to give you a helping hand if you really are interested.

I'd love to see this too!

SamanthaMarquez said:
It's really not that difficult. I didn't really like the CM mod either, so created my own stock rom. I'm now at the point where I got it all working. I don't mind to give you a helping hand if you really are interested.
Click to expand...
Click to collapse
Hey,
yes I've VERY interested...I'm hoping to get a stock-ish one together with my own little touches...maybe release one if I learn enough about it.
Any help you can give would be much appreciated...
Even to start with, a list of the basics...ie get ROM dump, extract xyz, do this...anything at all...
I just got back from a swim at the beach to relax, intending to come back and try to figure it out on my own with what help I can get from that page linked above...but if you have managed to get one together, thats even better

This might be of some use for windows users (I've successfully tried extracting MDJ's Gingerbread system.img with it).
http://android.modaco.com/content/z...-boot-recovery-system-userdata-kitchen-ready/

yea extracting is easy...but I would prefer to use a clean build to start from, rather than m-deejays...trying it using the guide in the link above with the Nexus S dump...having to use some donor files from m-deejays build though...still trying to get my head around it all

Well I gave it a quick try using the above guide, and it gives "NAND Kernel Open Fail".
I used m-deejays kernel, and put all the relevant files into the correct directories before making the system.img, and i put initrd.gz and zimage into boot.img, so I dont know what I did wrong...?

You don't use system.img on nand. You need to create a yaffs.img. Which I've never done before. I've only made builds the sd way, not nand. Maybe all you have to do is rename the .img after you create it. You should jump on irc, room #htc-linux-chat. You would get your answer in like 5 secs;p

NAND ROMs do use system.img, have a look in any NAND ROM, you'll see system.img, boot.img and the flash files.
Yaffs is the filesystem...I created the img files with the "mkyaffs2image" command.
(As per this thread: http://forum.xda-developers.com/showthread.php?t=897940)
I've made all of these but get the damn kernel error...it can't be difficult, lots of devs have released ROMS...surely someone is willing to help?
I'd rather not go into irc, as thats the dev channel isnt it? Dont want to be a noob popping in asking hwo to cook Android for the HD2

i think what would be a cracking idea is if someone were to create 3 "standard" kitchens for anyone to download and start modding with.
kitchen 1) desire / desire HD with NO mods
kitchen 2) Froyo / gingerbread with NO mods
kitchen 3) Froyo / gingerbread with Cyanogen included
they should just be 100% stock but able to build a fully working rom. This way everyone can start to learn, and its always easier with a complete kitchen and just as educational - moreso as you get to see the correct layout for files / directories and all the correct tooling is already in place.
I will add to davids "donation" pot if someone were to make these available, whatever david is willing to donate and i will add another $20 (US) or £15
Whether they be Windows or Linux based kitchen does not matter to me, but i believe that android being open source these resources should be made available
G

Your right, not thinking clearly from all the jack daniels. You do need yaffs tools to mess around with the system.img though...#htc-linux is the dev channel. #htc-linux-chat is where you go to ask questions. Devs don't even go in that channel. Just chefs fire the most part. That's where everyone goes to learn how to build.

g.lewarne said:
i think what would be a cracking idea is if someone were to create 3 "standard" kitchens for anyone to download and start modding with.
kitchen 1) desire / desire HD with NO mods
kitchen 2) Froyo / gingerbread with NO mods
kitchen 3) Froyo / gingerbread with Cyanogen included
they should just be 100% stock but able to build a fully working rom. This way everyone can start to learn, and its always easier with a complete kitchen and just as educational - moreso as you get to see the correct layout for files / directories and all the correct tooling is already in place.
I will add to davids "donation" pot if someone were to make these available, whatever david is willing to donate and i will add another $20 (US) or £15
Whether they be Windows or Linux based kitchen does not matter to me, but i believe that android being open source these resources should be made available
G
Click to expand...
Click to collapse
Yea, something like that would be handy...but even to start with, I'd just love to know the basic processes needed to get a basic Android build running on the HD2, without having to rely on someone elses current build.
I tried the link above, and it did sort of help understand a little of whats going on...but this stupid kernel error is preventing me from knowing how my test build works/or doesnt work...
I mean I had too use m-deejays gingerbread dump to get some of the driver files etc from...but where does he get them from? Thats the stuff I dont know...
It's obviously not overly difficult as there are so many devs pumping out HD2 ROMs...would just love one of them to share the secrets
Cash - not sure ... depends on how much help I get, but I'm willing to donate along the lines of US$20 or so...
mattfmartin said:
Your right, not thinking clearly from all the jack daniels. You do need yaffs tools to mess around with the system.img though...#htc-linux is the dev channel. #htc-linux-chat is where you go to ask questions. Devs don't even go in that channel. Just chefs fire the most part. That's where everyone goes to learn how to build.
Click to expand...
Click to collapse
hehe...
What server is that chat room on?

the_scotsman said:
NAND ROMs do use system.img, have a look in any NAND ROM, you'll see system.img, boot.img and the flash files.
Yaffs is the filesystem...I created the img files with the "mkyaffs2image" command.
(As per this thread: http://forum.xda-developers.com/showthread.php?t=897940)
I've made all of these but get the damn kernel error...it can't be difficult, lots of devs have released ROMS...surely someone is willing to help?
I'd rather not go into irc, as thats the dev channel isnt it? Dont want to be a noob popping in asking hwo to cook Android for the HD2
Click to expand...
Click to collapse
Is it possible that the img files need to be created as ext4 rather than yaffs? I know gingerbread runs on the ext4 system (where froyo ran on yaffs2) but I'm not sure how this relates to building the rom.

Nah, don't think so...not accroding to: http://forum.xda-developers.com/showthread.php?t=897940
Ive tried a few more times but am still getting the kernel error...so I cant even test if my build works or not as it wont even boot...so very frustrating...

Lets break it down........
1st
Here's a brief intro I did a few days ago read it..
http://forum.xda-developers.com/showthread.php?t=897940&page=2
The above goes for any .img used with DAF, they are yaffs2 images.
2nd
The sensible option for a clean build would be an existing stock gingerbread rom on a sister device. AdamG just happens to make the cleanest Desire roms around. I've had my eyes on this build for a minute, check it out and see if this what your looking for. Oxygen v2.0-RC6
3rd
I've been able to unyaffs disect, reassemble and get some 'customized' roms running. They flash, boot, & work great.....but I lose root permissions. lol
I was acutally doing this with the 1.6 NAND rom of MDJ that came as a single.img
That particular file was just system.img & boot.img yaffs2'd together. After I disected it I was able to unyaffs the 2 images and edit/modify change kernels, etc. etc. The only problem I have run into is the root issue.
Conclusion:
----------------------------------------------------------------------------
I'd be glad to help out any way I can in porting a ROM worthy of our devce
Any serious inquries can be directed to my inbox for private discussion on gtalk .
I'm no dev and am in no way claiming to be. I do have some findings and that's why I'm offering my help. Cheers

[DEV] CM7 (CyanogenMOD 7, Gingerbread) on Captivate, for Developers only

For developers only!! We are not supporting users yet
The instructions to build Gingerbread are on http://cmsgs.com
If you intend to develop for Captivate, you are welcome to use the instructions to build from source and test/debug/fix. This is not for the average user right now and we ask that you do not post binaries for users because things are unstable and we'd really rather not be dealing with users who've managed to screw up their phones.
There are two steps initially - first is to flash and convert filesystems, update recovery, kernel and CM7, but after that you can just install the CM7 zip if you have done another rebuild as you do development.
There is no easy way of going back to froyo - you would have to flash to stock via Odin one-click and let it blow away the filesystem etc. This is why it is for developers only - it is very alpha and you will find yourself going back and forth a lot.
Warning - this will eat your kitties and possibly your doggies and goldfish too!
-Atin

I dont mean to ruin the thead but, just want to say thanks to all devs working on cm7! And look foward to running cyanogen again after using on my htc magic a couple years ago!

Building right now...I am the excite.

good stuff.
can't wait to see the first gingerbread rom on captivate.

Trusselo said:
i hope your ROM building is better than your sentence building
Click to expand...
Click to collapse
Why the hate? Take a chill pill.....

shawn122 said:
Why the hate? Take a chill pill.....
Click to expand...
Click to collapse
Because he likes to act like a little kid in just about any thread that he can.
There's always gotta be one douchebag.
Anyways, let's keep this thread clean.

That **** isn't needed here. Building now and pretty stoked. Thanks!

I am the excite.

Im interested in trying to impliment voodoo sound. Ive been following this http://code.google.com/p/cyanogenmod7-for-samsung-galaxys/issues/detail?id=16 and it looks like it wouldnt be too hard. Any ideas on how easy or hard this really is or what i could try to do on my end to try to add from supercurio's repo? *see his nexus S thead from the link above*

Thanks in advance for all those who cook up some GREAT ROMS!!!

atinm said:
For developers only, the instructions to build Gingerbread are on http://cmsgs.com
If you intend to develop for Captivate, you are welcome to use the instructions to build from source and test/debug/fix. This is not for the average user right now and we ask that you do not post binaries for users because things are unstable and we'd really rather not be dealing with users who've managed to screw up their phones.
Warning - this will eat your kitties!,
-Atin
Click to expand...
Click to collapse
Getting errors on sync. 'Bad head' not at my computer so can't get exact error

cchant said:
Getting errors on sync. 'Bad head' not at my computer so can't get exact error
Click to expand...
Click to collapse
Try again - seems to be working here.

bamonkey said:
Im interested in trying to impliment voodoo sound. Ive been following this http://code.google.com/p/cyanogenmod7-for-samsung-galaxys/issues/detail?id=16 and it looks like it wouldnt be too hard. Any ideas on how easy or hard this really is or what i could try to do on my end to try to add from supercurio's repo? *see his nexus S thead from the link above*
Click to expand...
Click to collapse
Since all the code is on github, both for voodoo sound and for CM7, you just need kernel/android smarts to pull in the changes. Clone the repos, take what you need . . . sorry I can't help more, I haven't looked at voodoo sound but there are others who have that could help I'm sure.

cchant said:
Getting errors on sync. 'Bad head' not at my computer so can't get exact error
Click to expand...
Click to collapse
Error in line 1380 of project.py, in GetHead fd = open(path, 'rb')

I got this error.
Code:
error: revision refs/heads/master in manifests not found

I got both of those. Clean repo

ballz0iron said:
Error in line 1380 of project.py, in GetHead fd = open(path, 'rb')
Click to expand...
Click to collapse
this is an error with repo/your machine, not CM7. try syncing again after a while (possibly after a reboot) or clearing out the folder (including your .repo folder) and trying again

ih4ckback said:
I got this error.
Code:
error: revision refs/heads/master in manifests not found
Click to expand...
Click to collapse
Actually I should clarify, I got that error trying to init the GB initial flash repo. Any assistance? I need to start there since I don't have it or do I not really need it?

ih4ckback said:
Actually I should clarify, I got that error trying to init the GB initial flash repo. Any assistance? I need to start there since I don't have it or do I not really need it?
Click to expand...
Click to collapse
Sorry guys - there should be a -b gingerbread on the repo init -u git://github.com/teamhacksung/android.git -b gingerbread, I've fixed the wiki page with the instructions for the initial flash.

atinm said:
Sorry guys - there should be a -b gingerbread on the repo init -u git://github.com/teamhacksung/android.git -b gingerbread, I've fixed the wiki page with the instructions for the initial flash.
Click to expand...
Click to collapse
I seeeeeee. Syncing now lol.

[REQ] 2WCR port or patch guide for AOSP-MIUI

Hi, I don't know the proper way of doing this but I do humble request to someone with spare time to make a PATCH or post some guide for patching at least the default MIUI kernel to have proper 2WCR on it.
I don't live in the US so 2WCR laws don't restrict me from recording my own calls.
Thank you in advance.

Is there a problem with the built-in method of 2wcr? I've never tried it, but it should work fine out of the box.
MIUzI weighs a ton.

EndlessDissent said:
Is there a problem with the built-in method of 2wcr? I've never tried it, but it should work fine out of the box.
MIUzI weighs a ton.
Click to expand...
Click to collapse
Built-in method from the EVO4G is only good if you make calls using the loudspeaker because it records from the MIC.

Wrong section my friend.

Sorry, I really didn't knew where to make the request, but I really hope someone has the spare time to make or help me accomplish this. If any moderator read this please be kind enough to move this thread to the appropriate section, and sorry for any inconvenience.

To Add it into the Kernel is pretty easy. Just replace 6 files in the source code of your Kernel with the ones from my www.github.com\detcup4evr
Sorry I haven't had a chance to look at ASOP kernel much, but code looks pretty similar.
Add these files
arch/arm/mach-msm/qdsp6/amrnb_in.c
arch/arm/mach-msm/qdsp6/vocpcm.c
Edit these or just replace
arch/arm/mach-msm/include/mach/msm_qdsp6_audio.h
arch/arm/mach-msm/qdsp6/Makefile
arch/arm/mach-msm/qdsp6/pcm_in.c
arch/arm/mach-msm/qdsp6/q6audio.c

Thank you very much for your response, I know it looks simple to do but for me those tips you gave me are like rocket science,I don't have the sightless idea on how to accomplish it but I will try to make some time to read and learn how to compile that, between work and my 2 kids I don't have too much spare time hehe, but I appreciate your kindness.

detcup4evr said:
Just replace 6 files in the source code of your Kernel
Click to expand...
Click to collapse
whether it is suitable for all devices, or for HTC only? e.g. will it work for LG O1, CM miks ROM?
thanks very much

detcup4evr said:
To Add it into the Kernel is pretty easy. Just replace 6 files in the source code of your Kernel with the ones from my www.github.com\detcup4evr
Sorry I haven't had a chance to look at ASOP kernel much, but code looks pretty similar.
Add these files
arch/arm/mach-msm/qdsp6/amrnb_in.c
arch/arm/mach-msm/qdsp6/vocpcm.c
Edit these or just replace
arch/arm/mach-msm/include/mach/msm_qdsp6_audio.h
arch/arm/mach-msm/qdsp6/Makefile
arch/arm/mach-msm/qdsp6/pcm_in.c
arch/arm/mach-msm/qdsp6/q6audio.c
Click to expand...
Click to collapse
Sadly it's not a cut and paste in the case of AOSP. I am having to rewrite of amrnb_in.c in order to evern suggest getting it to compile. I strongly discurage anyone from copy and pasting those files over as the have dependencys on things that come with sense that are simply not in AOSP.

vocpcm and qdsp6
atyoung said:
Sadly it's not a cut and paste in the case of AOSP. I am having to rewrite of amrnb_in.c in order to evern suggest getting it to compile. I strongly discurage anyone from copy and pasting those files over as the have dependencys on things that come with sense that are simply not in AOSP.
Click to expand...
Click to collapse
Hi, did anyone get this working ok ? I just tried the suggestion above but it seems like I am missing a bunch of dal headers etc.
Is it just working on specific Qulacomm DSPs in HTC devices ? I have for example a qdsp6v2_1x directory in my HTC sources for HTC Sensation
Anyone tried to build this on kernel 3.x ?
cheers
Mark