Related
Hey there devs. I just fixed A2DP for VanillaEclair, and I have to share this. Now we can all provide full-featured AOSP-roms, so good luck with tweaking your kernels!
Apparently the solution was simplier than we all thought. We had a missing bluetooth firmware file. Put this to /system/etc/firmware and you'll get A2DP working properly. I got this idea from Darchstar, while I was looking at the firmware file in his rom. Damn... we could've fixed this months ago! So... enjoy and let the fun begin!
PS: unzip this, of course...
Ah, you little bugger You beat me to it.
I actually saw this yesterday while trying to pull proprietary files to compile Cyanogen's Hero port, and noticed that this exact file was missing from my phone. I didn't take too much notice of it until I realized what 'brf' could stand for (Bluetooth Radio Firmware). Was just busy experimenting around this morning
Anyway, well done on the fix - you've made a lot of AOSP lovers happy Might I suggest that you possibly look for further missing files that may solve some other hardware bugs (maybe trackball LED?). I'll see what I find missing today in the ROM.
Mr P.
solved yesterday ....
You've ported Darchstar's ROM, eh? Damn file, this could have been solved for ages. But it's good to have it now anyway.
cheer for you
missing firmware? I had a feeling the problem would be very simple
gonna try this on aHero .. thanks man
RaduG said:
You've ported Darchstar's ROM, eh? Damn file, this could have been solved for ages. But it's good to have it now anyway.
Click to expand...
Click to collapse
but what I think is not enough in some cases, I also worked on the driver liba2dp
The firmware file itself fixes the issue. Nothing else is required.
great! it works! thx
RaduG said:
The firmware file itself fixes the issue. Nothing else is required.
Click to expand...
Click to collapse
I have not had a chance to test it with my edits, though I now also works on bluetooth transfer after work on liba2dp
Now we have it sticky. Thanks Fallen Spartan!
robin04 said:
but what I think is not enough in some cases, I also worked on the driver liba2dp
Click to expand...
Click to collapse
One thing to keep in mind: although the term A2DP is thrown around a lot when talking about bluetooth audio, A2DP has been working fine for a while now. A2DP is the bluetooth profile for high quality uni-directional stereo sound. HFP and HSP are the profiles that allow you to actually talk to someone on a call.
en.wikipedia.org/wiki/Bluetooth_profile
It doesn't make much of a difference when conversing with others on the forums, but if you are actually diving into code it makes a huge difference.
This is ignoring the fact that the problem could have been bluetooth not switching away from A2DP properly or some other such problem, but that didn't seem to be the case because headsets that don't support A2DP still did not work right. This is also assuming that the bluetooth stack in these devices don't depend on A2DP code for all audio over bluetooth as I have not looked at much of the code.
If you already know this, then sorry for the post, but if you didn't, it might save you many hours of banging your head against the wall. On the other hand, if you know for certain that the A2DP code is used when making a call, I'd like to know that as well so I don't get frustrated figuring out how it all ties together.
Derek
Nebvin said:
One thing to keep in mind: although the term A2DP is thrown around a lot when talking about bluetooth audio, A2DP has been working fine for a while now. A2DP is the bluetooth profile for high quality uni-directional stereo sound. HFP and HSP are the profiles that allow you to actually talk to someone on a call.
en.wikipedia.org/wiki/Bluetooth_profile
It doesn't make much of a difference when conversing with others on the forums, but if you are actually diving into code it makes a huge difference.
This is ignoring the fact that the problem could have been bluetooth not switching away from A2DP properly or some other such problem, but that didn't seem to be the case because headsets that don't support A2DP still did not work right. This is also assuming that the bluetooth stack in these devices don't depend on A2DP code for all audio over bluetooth as I have not looked at much of the code.
If you already know this, then sorry for the post, but if you didn't, it might save you many hours of banging your head against the wall. On the other hand, if you know for certain that the A2DP code is used when making a call, I'd like to know that as well so I don't get frustrated figuring out how it all ties together.
Derek
Click to expand...
Click to collapse
I'm not banging my head. mine is the first rom that works on bluetooth audio.
However, as I wrote in the post, in some cases may be associated with
A2DP, in fact, I added the firmware missing
Regards,
robin04
robin04 said:
I'm not banging my head. mine is the first rom that works on bluetooth audio.
However, as I wrote in the post, in some cases may be associated with
A2DP, in fact, I added the firmware missing
Regards,
robin04
Click to expand...
Click to collapse
Like I said, if you already know all of that, then sorry for posting it. There are many on these forums that don't know the difference though, so maybe it will help them. Most headsets don't even support A2DP, my Jawbone Icon only recently got support for it (yay!).
I currently use your rom as I need one with a BFS kernel. The Audible beta app runs with barely any stuttering with it, whereas those with higher end devices are complaining about the poor performance. Thanks!
Derek
What's the point in saying you have fixed it first if you didn't even bother to share? Many things appeared in my ROM for the first time, but I didn't even mention it. We both went out on kicking some guy's ass because he wasn't helping the community, but it seems that you didn't have that in mind either.
Anyway... now everything works in the Vanilla ROMs and that's good.
RaduG said:
What's the point in saying you have fixed it first if you didn't even bother to share? Many things appeared in my ROM for the first time, but I didn't even mention it. We both went out on kicking some guy's ass because he wasn't helping the community, but it seems that you didn't have that in mind either.
Anyway... now everything works in the Vanilla ROMs and that's good.
Click to expand...
Click to collapse
I've simple answered nebvin ....
I do not understand why you have to start a war for anything.
I was going to share (you ask xenoside) but have not had time to make a package to flash.
collect information before judging.
Regards,
robin04
I knew it! I knew it! I knew it! Why did I not follow my instincts on this! I saw all the other ROMs from the G1 area and they had this file. But I should have realized it!
RaduG what's the difference between this and brf6300.bin? Do we need both?
I don't think we need brf6300.bin. Here's the difference:
BRF6300
The BlueLink 5.0 platform from TI is a highly integrated, digital CMOS, single-chip solution supporting Bluetooth® Specification v2.0 and all software needed for Bluetooth operation.
Click to expand...
Click to collapse
BRF6350
The BlueLink 6.0 platform from TI,BRF6350, integrated device includes Bluetooth baseband, RF transceiver, ARM7TDMI®, memory (ROM and RAM), power management and an FM receiver.
Click to expand...
Click to collapse
So these are two different chips, and we have only one inside our heros. What's curious is the fact that the taiwan 2.1 ROM only included BRF6300 firmware and A2DP works with that. One more interesting think is that apparently BRF6350 includes an FM reciever, so in theory we might be able to get the radio functionality.
I see. Thanks!
Release thread here: http://forum.xda-developers.com/showthread.php?t=739730
any question plz post them on my thread over at the touch pro forums, this release was tested on Raph110 i have no idea how it will perform in your device
Screen Shots:
it works i can confirm it and damn is it fast had to move some files over from 2.2 but wow what a difference 1.6 on sprint touch pro 2 rocks will report more findings as i get them
siulmagic said:
Release thread here: http://forum.xda-developers.com/showthread.php?t=739730
any question plz post them on my thread bare in mind, this release was tested on Raph110 i have no idea how it will perform in your device
Screen Shots:
Click to expand...
Click to collapse
1.6 on sprint touch pro2
ok so i got it set-up and if you want to try it and someone can show me or host the files for me im willing to share but so far its great call volume is drum breaking now please note all i have is the config file for sprint and i know vz's is different but i can tell you how to get it
Curious
Does this need to have the orginal project android installed? Also, will this run on T-Mo? Lastly, does gps work?
couldnt honestly answer it but no it doesnt need any other android project no gps wont work i read in the other post something about legacy but i dont see why it wouldnt run on t-mobile
outerdepth said:
Does this need to have the orginal project android installed? Also, will this run on T-Mo? Lastly, does gps work?
Click to expand...
Click to collapse
outerdepth said:
Does this need to have the orginal project android installed? Also, will this run on T-Mo? Lastly, does gps work?
Click to expand...
Click to collapse
GPS should work. Thats kernel controlled, not OS controlled.... works on all of my builds 2.0.1 - 2.2
siulmagic said:
i can put that up but.. most ppl know camera is not working on our kernel, dint think it was necessary to specify that.
Click to expand...
Click to collapse
Should also mention in the link for the Rhodium that got added to our thread that HW3D, BT, and Sound are not working for Rhodium. This will confuse people. lol
it seems i did not make it clear on my post, when i said "any question plz post them on my thread " i meant the thread over in the touch pro forums not here, so again sorry if mislead you.
I'm bhoping gps works...lol..works on mine..lol
Sent from my MSM using XDA App
TMobile TP2
I see the builder uses AT&T will this work on US Tmobile? if not can some tell me where I can find them I have been search several pages so far this is the only one I have found.
Thanks
how is the battery
how is the battery in this build?
bobsnag said:
how is the battery in this build?
Click to expand...
Click to collapse
same as in xdandroid?
Well, if BT works, what about the camera, wifi & charging?
m4f1050 said:
Well, if BT works, what about the camera, wifi & charging?
Click to expand...
Click to collapse
Did you even try it...? Or read about it...?
I think BT is in the same state as all the other builds... I'm going to make a wild assumption and say that camera, wifi and charging are as well.
But, give it a whirl and let the OP know how it went. Obviously the camera is not going to work and BT will probably pair but not work either.
arrrghhh said:
Did you even try it...? Or read about it...?
I think BT is in the same state as all the other builds... I'm going to make a wild assumption and say that camera, wifi and charging are as well.
But, give it a whirl and let the OP know how it went. Obviously the camera is not going to work and BT will probably pair but not work either.
Click to expand...
Click to collapse
Eventually I will, I just have 2 other builds im testing and a 3rd one will fill my plate to the point I wont be able to test any! :O But yeah, looks promising, considering my phone has alaways booted, never had flashing issues or android boot issues...maybe you're right and it "sorta" works, because I have Wifi working on xdandroid froyo 2.2 and a lot of people don't...
m4f1050 said:
I have Wifi working on xdandroid froyo 2.2 and a lot of people don't...
Click to expand...
Click to collapse
Everyone else has wifi working too... unless you are using WEP. VERY rarely some of the T-Mobile tp2s don't work, but for the most part you're not special.
Sent from my SAMSUNG-SGH-I897 using XDA App
Oh..... Bummer! LOL!
Thanks... Testing now.
I'm sorry if this has been brought up before. I am new to the forums but have been following the forums for a while.
I have a rooted HTC Incredible (2.2) and I recently ordered a bluetooth keyboard for typing and playing games. I have been reading about how HTC phones do not use an updated bluetooth stack.
After coming across that, I started searching for a solution. I have been searching for weeks and still haven't come across a definite answer. With that being said, does anyone have any information on how I would go about updating the bluetooth stack to a stock Android version so it is usable with the new keyboard?
Thank you in advance!
So, I recieved my keyboard today and of course, it doesn't connect. Now, the weird thing is, is that it claims to be compatible with Android 1.6+. Doesn't HTC use a Bluetooth stack from 1.6?
Any help would be great.
ijustintouch said:
So, I recieved my keyboard today and of course, it doesn't connect. Now, the weird thing is, is that it claims to be compatible with Android 1.6+. Doesn't HTC use a Bluetooth stack from 1.6?
Any help would be great.
Click to expand...
Click to collapse
Try cm6/7 they updated the Bluetooth stack to the latest compatable
Sent from my ADR6300 using XDA App
Awesome! Thank you so much.
It works perfectly. This is going to make playing games and typing emails and even doing school work on the go soooo much easier!
I can not thank you enough.
ijustintouch said:
Awesome! Thank you so much.
It works perfectly. This is going to make playing games and typing emails and even doing school work on the go soooo much easier!
I can not thank you enough.
Click to expand...
Click to collapse
No problem
Sent from my ADR6300 using XDA App
Since, frx07 is coming out sooon. What are features that are coming with it or fixes ?
Sent from my MSM using XDA App
madplaya1 said:
Since, frx07 is coming out sooon. What are features that are coming with it or fixes ?
Sent from my MSM using XDA App
Click to expand...
Click to collapse
There will be a formal list when it drops. I will make a thorough post of what's changed when the time is right.
The big ones are RIL & BT. Audio routing won't make FRX07, so BT audio won't work, but pairing with BT devices & transferring data should.
Great , thanks!
Sent from my MSM using XDA App
seems silly to me to evenrelease fr0x7 without the BT and the audo routing fixes already in place at least for the rhodium users., i understand that the BT and audio routing fixes are mostly RHOD specific so why not make 2 version's of FR0x7? Those are the changes that most ppl weant they want there BT and loud speakerphone. Just curious as to why it would even be released without those things since the fixes are out, if it means having to wait to release fr0x7 than wait IMO. i donno just my 2 cents
Audio routing isn't stable,isn't for all the devices and it's still being developed
So it's a time waste adding it now,then frx08 will have it..
helicopter88 said:
Audio routing isn't stable,isn't for all the devices and it's still being developed
So it's a time waste adding it now,then frx08 will have it..
Click to expand...
Click to collapse
Couldn't have said it better myself. Audio routing will not be implemented until it's stable.
Shouldn't the dev start focusing more on gingerbread because it's newer, just wondering? Or what?
Sent from my MSM using XDA App
madplaya1 said:
Shouldn't the dev start focusing more on gingerbread because it's newer, just wondering? Or what?
Click to expand...
Click to collapse
If you think GB has been forgotten, you are sorely mistaken. Your thread asked about FroYo, so that's what we've been talking about...
Lol ok
Sent from my PG06100 using XDA App
hi there every1,
i was wondering if there is gonna be a working Camera in FRX07 for us Rhod100_nl users with the wrong board??
grtzzzz
bArAbAts said:
hi there every1,
i was wondering if there is gonna be a working Camera in FRX07 for us Rhod100_nl users with the wrong board??
grtzzzz
Click to expand...
Click to collapse
Kernel issue, not a build issue from what I can tell.
Also, from what I've gleaned - the cam works, but only in low light. See
[UPDATED 04/29][DEV - Camera ( camcorder improvement ) ] Camera tests for more information.
Bluetooth data would be great. I have an asus transformer which will not connect to an adhoc network, so WiFi tethering is out. The only solution I can find for tethering a honeycomb tablet is through pdanet tablet, which requires android on both devices and uses bluetooth. Thanks for all the hard work.
EMB Driver said:
Bluetooth data would be great. I have an asus transformer which will not connect to an adhoc network, so WiFi tethering is out. The only solution I can find for tethering a honeycomb tablet is through pdanet tablet, which requires android on both devices and uses bluetooth. Thanks for all the hard work.
Click to expand...
Click to collapse
Is there a wpa supplicant hack for the transformer? My A500 tablet has the same issue stock, but with mod or custom ROM wifi tethering to my rhodium works perfect on ad-hoc. Anyway, maybe worth looking into.
PlacidFury said:
Is there a wpa supplicant hack for the transformer? My A500 tablet has the same issue stock, but with mod or custom ROM wifi tethering to my rhodium works perfect on ad-hoc. Anyway, maybe worth looking into.
Click to expand...
Click to collapse
Yes there is. I'm on an adhoc posting this from my TF right now. check the TF section for the xoom supplicant file or just flash prime 1.5 as this fix is already implimented in that rom
Will it have the new MMS fixes? That's the biggest thing missing for me. People love to send pictures and I always have to boot WiMo and ask them to resend it.
gallahad2000 said:
Will it have the new MMS fixes? That's the biggest thing missing for me. People love to send pictures and I always have to boot WiMo and ask them to resend it.
Click to expand...
Click to collapse
Yes, it will work for all carriers assuming you set your APN. Still hashing out the best way to do this, might just have to leave it up to the end-users to configure.
I flashed prime on my TF last week. Works great and has the WPA supplicant fix already built in.
I can tether to my TP2 in winmo or whatever! Works GREAT.
Also, waiting for FRX07. Great work on FRX06!
@arrrghhh, tnx for your reaction, but im not an android expert, is there a way to implement the fixes mentioned there in frx07??
keep up the good work!!
tnx!
bArAbAts said:
@arrrghhh, tnx for your reaction, but im not an android expert, is there a way to implement the fixes mentioned there in frx07??
keep up the good work!!
tnx!
Click to expand...
Click to collapse
Not easily, there's many, many changes. The easiest way would be to pull from the XDAndroid repo (all of our code is available...) and build your own system image.
07 will be out soon. In the final stages of testing.
arrrghhh said:
Not easily, there's many, many changes. The easiest way would be to pull from the XDAndroid repo (all of our code is available...) and build your own system image.
07 will be out soon. In the final stages of testing.
Click to expand...
Click to collapse
Is there a thread or website that shows the info on FRX07
Hey folks,
This is a completely new build, with all the new changes baked in. We wanted to do a semi-official test release to collect bugs and hopefully do a formal official release with everything settled. The main pain point is the CSV files (see pre-install prep).
So a brief overview:
New acoustic routing code baked in. Should fix most if not all audio routing problems, and will provide more debugging if stuff does go wrong. Also allows for more granular tweaking, see the CSV files.
GPS fixes for GB - GPS not only works in GB now, but it doesn't kill sleep! I was able to use GPS, get a solid lock, and put the device to sleep no problem.
BT should work & well with the new acoustic code. Post results.
RHOD users now have a choice of kernels. .35+ all have the new acoustic - so .35, .39, 3.0 and 3.1 are all fair game now... This is bundled with .27!!
Keep in mind, autobuild .27 kernels will produce no audio in this build... Obviously the bundled kernel will work, and the absolute newest .27 autobuild kernel does work now - Feb.27 2012 or newer.
rootfs tweaks - first, it will detect which kernel you're on (.27 or .35+) and automatically apply the correct firmware. Second, is it will always copy/extract the modules... failures there were getting annoying, and this is surefire if brute-force...
Few Easter egg apk's...
Probably a lot I'm forgetting, this might change
Pre-Install Prep REQUIRED!!!
This step is crucial, and I forgot all about it! You must copy all of the *.CSV file from your WinMo ROM - these are in the \Windows\ directory. There's a very easy way to do this. It involves the Total Commander app for WinMo (Direct Link for the perpetually lazy...) (included in EnergyROM and others probably).
Now you're in Total Commander looking at your \Windows\ directory. Whew... lots of files. Fear not! Hit the "CTRL" button, then the green "Plus" button. This opens the Select/Unselect files dialog. Put in *.csv, press "select" and voila. All CSV files are selected. Now - File -> Copy/Move -> I want you to copy these (should be 10) files to the ROOT of your SD card. No folders!!! This is hardset right now, until we get it all implemented into the build properly. Thanks!
Install
Assuming you've done the pre-install prep; this is installed just like the other XDAndroid builds - grab your startup.txt (don't forget rel_path= if you don't have it at the root of the SD!), ts-calibration and boot!
Download
Caveats:
Audio stutters every 10sec. The only fix I've heard is using a kernel from G3rmo (unfortunately it is old), or
Code:
su
kill -9 28
Which kills the [battery] process. I'm sure this will have negative effects on the battery meter/battery life...
SD Card not working...? "Waiting for SD Card" appearing on boot...? Try putting this command in your startup.txt
Code:
msmsdcc_1bit msmsdcc_fmax=14000000 msmsdcc_nopwrsave
See gummbah30's post reminding us of these commands.
SD Card has partitions? (If you used a non-XDAndroid build the answer is YES) Then you need to add "no_partitions" to your startup.txt. Between the quotes on the set cmdline line. Do not put it on its own line, it goes in between the quotes! Make sure there is one space between each item.
BT might still be flaky
The CSV files from my BLAC100 are attached for the lazy. I'd like to gather CSV's from each RHOD, I'm curious if any ROM devs have changed them out either... This could get interesting. If you folks don't mind, post up your CSV's, point out differences with mine, etc... We're trying to figure out how to unify these, if possible! Thanks!
Keyboard tiny/unusable? Either change the IME (long press on the input box) Get rid of it! I've heard "Hackers Keyboard" is a good alternative - many options. There's also "Better Keyboard", Swype, etc... Side load the APK using AndroidApps, adb install, etc.
Please post back any issues, enjoy!
GBX0C Changelog
Camcorder: Now works (tested on rhodium).
Acoustic: Bug-fix : correct random loss of dual(rear)-mic.
MMS: Bug-fix: Slides with zero duration on Sprint.
Gps: Bug-fix: Init/de-init sequence fix (correct gps not starting up after being unchecked in Settings).
Gps: Bug-fix: End gps session with a correct rpc call (relevant to amss6125 devices).
Gps: Bug-fix: Don't send delayed position requests after session has ended (possibly relevant to Navigation issues).
Gps: New feature: Xtra (aGPS) -> verified to work on rhodium/cdma raph.
X1 specific: Screen rotation patch.
Added tytung's GPS injector app to AndroidApps\Other as well as updating/cleaning up some apps in AndroidApps.
Modified rootfs for newest apsta firmware & wifi firmware - wifi tethering now works flawlessly in the newest kernels! .27 is still bundled for the record...
logcat attached
just like to say speakers when making a call works........loud rear speakers (speakerphone) don't work nor does sound in touch selection when going threw screen selection and playing music does not work also.....hope this helps
welard said:
just like to say speakers when making a call works........loud rear speakers (speakerphone) don't work nor does sound in touch selection when going threw screen selection and playing music does not work also.....hope this helps
Click to expand...
Click to collapse
Interesting, does any sound work...? Does it play thru the earpiece instead of the rear speaker? What about previewing ringtones? Next time you pull a logcat, make sure to use -v time. Using GetLogs makes it much easier .
Thanks for testing btw. The more the merrier! If we're going to make this change global, we want to make sure no devices are left in the dust. So it's up to you guys to test and ensure that it works properly! If it doesn't, we'll try to fix it.
If anyone feels like hopping on #xdandroid on freenode while testing, that would be great! Thanks again!
i attached the file i found on sd card after pulling the logs with getlogs. i hope this is the file you wanted.
i just added following commands to my startup, because i cant boot without them:
msmsdcc_1bit msmsdcc_fmax=14000000 msmsdcc_nopwrsave
am20033 said:
i attached the file i found on sd card after pulling the logs with getlogs. i hope this is the file you wanted.
i just added following commands to my startup, because i cant boot without them:
msmsdcc_1bit msmsdcc_fmax=14000000 msmsdcc_nopwrsave
Click to expand...
Click to collapse
Those commands are necessary if you have a SD card that doesn't play nicely. If you need 'em, put 'em in.
Thanks for the logs, I'll pass them on. Anything you can say about 'em? What happened during the logs...? Please be as specific as possible. The more information, the better.
Bump...
I made a mistake. Messed up bad folks! I forgot an extremely crucial step... See the first post! Pre-install Prep .
am20033 already has given pretty good feedback, once having done this step. So send it through the ringer guys, c'mon!
arrrghhh said:
Bump...
I made a mistake. Messed up bad folks! I forgot an extremely crucial step... See the first post! Pre-install Prep .
am20033 already has given pretty good feedback, once having done this step. So send it through the ringer guys, c'mon!
Click to expand...
Click to collapse
wooooow......thats all i can say......loudspeaker in call works perfect.... incall audio perfect.......touchsceen click works well......overall system louder......have not tested music but in (sound settings)....ringtone, media and alarm works well...bluetooth audio headset has lots of background noise u can hear the other person but not very well but audio is rooted to bt headset.....will test further and report back asap......
p.s. there are 5 c.s.v file in window mobile on blackstone....ive re-check and found 5.....if anyone find more please let me know, but far as i know there is 5 not 10.....thanks
welard said:
wooooow......thats all i can say......loudspeaker in call works perfect.... incall audio perfect.......touchsceen click works well......overall system louder......have not tested music but in (sound settings)....ringtone, media and alarm works well...bluetooth audio headset has lots of background noise u can hear the other person but not very well but audio is rooted to bt headset.....will test further and report back asap......
p.s. there are 5 c.s.v file in window mobile on blackstone....ive re-check and found 5.....if anyone find more please let me know, but far as i know there is 5 not 10.....thanks
Click to expand...
Click to collapse
Good deal! Some headsets seem to work better than others - we'll have to work on that once everything has settled. Glad everything else is working well!
As for there only being 5 CSV's, that might be true for Blackstone. What WinMo ROM are you on...? Perhaps some other users can verify. On my RHOD running EnergyROM there's definitely 10 CSV files in \Windows\. I might ask everyone post theirs so we can detect any differences - so if anyone would like to post all the CSV's they have in a zip file here that would be great!
arrrghhh said:
Good deal! Some headsets seem to work better than others - we'll have to work on that once everything has settled. Glad everything else is working well!
As for there only being 5 CSV's, that might be true for Blackstone. What WinMo ROM are you on...? Perhaps some other users can verify. On my RHOD running EnergyROM there's definitely 10 CSV files in \Windows\. I might ask everyone post theirs so we can detect any differences - so if anyone would like to post all the CSV's they have in a zip file here that would be great!
Click to expand...
Click to collapse
im on window 6.5 kwbr rom,....im not sure if files are different than in the orignal 6.1 for blackstone........thanks
welard said:
im on window 6.5 kwbr rom,....im not sure if files are different than in the orignal 6.1 for blackstone........thanks
Click to expand...
Click to collapse
Post those CSV's if you could!
arrrghhh said:
Post those CSV's if you could!
Click to expand...
Click to collapse
hear are my csv's......thanks...
arrrghhh said:
Post those CSV's if you could!
Click to expand...
Click to collapse
Thank's Arrrghhh , that is my best news today .
I'm a former HD owner and today i have a HD mini Photon , my current Android ROM is working very well .
The only real problem for me is the audio routing . Could you give me some help to test this in Photon? I can try to change my ROM in order to apply your fix. Don't worry if i don't have success doing that , i know devices are not the same and i don't disturb you .
Because this is HD forum if you want you can PM me.
Thank's a lot
cbolumar said:
Thank's Arrrghhh , that is my best news today .
I'm a former HD owner and today i have a HD mini Photon , my current Android ROM is working very well .
The only real problem for me is the audio routing . Could you give me some help to test this in Photon? I can try to change my ROM in order to apply your fix. Don't worry if i don't have success doing that , i know devices are not the same and i don't disturb you .
Because this is HD forum if you want you can PM me.
Thank's a lot
Click to expand...
Click to collapse
If you're on a native Android device and you're having audio routing problems I would talk to the developer of the ROM. If you re-read the first post, I detail why we have audio routing problems to day, and why this test build fixes those issues.
Your issue is completely different and entirely unique compared to our woes. Sorry.
arrrghhh said:
If you're on a native Android device and you're having audio routing problems I would talk to the developer of the ROM. If you re-read the first post, I detail why we have audio routing problems to day, and why this test build fixes those issues.
Your issue is completely different and entirely unique compared to our woes. Sorry.
Click to expand...
Click to collapse
Thank's arrrghhh , Photon is a WM 6.5 device (maybe the last HTC WM device) and the issue is the same I had in my blackstone for two years. (BT pairing but not audio ) it was my bigger problem there and with photon .... having the same problem..
I'm reading some times the blackstone thread looking for some light about this issue and today i found your thread. Trust me , the issue is the same and the way to resolve it must be similar.
I had success booting android HD blackstone roms in photon (more or less) and i will try to test your build. at the moment the booting animation start well but never end.
I'm changing some modules to obtain a bootable build but i don't know which libs or kernel modules are you changing here.
Thank's
cbolumar said:
Thank's arrrghhh , Photon is a WM 6.5 device (maybe the last HTC WM device) and the issue is the same I had in my blackstone for two years. (BT pairing but not audio ) it was my bigger problem there and with photon .... having the same problem..
I'm reading some times the blackstone thread looking for some light about this issue and today i found your thread. Trust me , the issue is the same and the way to resolve it must be similar.
I had success booting android HD blackstone roms in photon (more or less) and i will try to test your build. at the moment the booting animation start well but never end.
I'm changing some modules to obtain a bootable build but i don't know which libs or kernel modules are you changing here.
Thank's
Click to expand...
Click to collapse
Oh I see.
Others have this same problem...? I'm wondering if it's your headset, or the port. Do you know how audio routing works on the port for the Mini? Is it a kernel-only affair, or does userland effect it...?
arrrghhh said:
Oh I see.
Others have this same problem...? I'm wondering if it's your headset, or the port. Do you know how audio routing works on the port for the Mini? Is it a kernel-only affair, or does userland effect it...?
Click to expand...
Click to collapse
Is a general problem , I don't know if the problem is only in the kernel but i can give you some issues we have with the sound:
- the stereo wired headset sound only works if we use headset with micro , if we use headset without micro the sound is mono.
- The fm radio sound only works if we start de FM radio in WM before run haret , in other case we have only 5 seconds sound in Android FM radio, after 5 seconds the sound stops suddenly.
- the loudspeaker and sound in general in incoming calls is very low.
- The Bluetooth headset and the bluetooth hand free paired without problems but not redirect the sound.
I think the problem is not so different you want fix here in blackstone.
cbolumar said:
Is a general problem , I don't know if the problem is only in the kernel but i can give you some issues we have with the sound:
- the stereo wired headset sound only works if we use headset with micro , if we use headset without micro the sound is mono.
- The fm radio sound only works if we start de FM radio in WM before run haret , in other case we have only 5 seconds sound in Android FM radio, after 5 seconds the sound stops suddenly.
- the loudspeaker and sound in general in incoming calls is very low.
- The Bluetooth headset and the bluetooth hand free paired without problems but not redirect the sound.
I think the problem is not so different you want fix here in blackstone.
Click to expand...
Click to collapse
The fixes here apply to MSM7k devices. I'm not sure what you would need to port it to other devices... pretty sure our kernel would not work on your phone. That's going to be the hurdle. I would encourage you to analyze the userland stuff tho - that certainly might be useful to you.
arrrghhh said:
The fixes here apply to MSM7k devices. I'm not sure what you would need to port it to other devices... pretty sure our kernel would not work on your phone. That's going to be the hurdle. I would encourage you to analyze the userland stuff tho - that certainly might be useful to you.
Click to expand...
Click to collapse
Thank's arrrghhh , the hD mini have the MSM7227 processor, i will follow here your work.
cbolumar said:
Thank's arrrghhh , the hD mini have the MSM7227 processor, i will follow here your work.
Click to expand...
Click to collapse
Don't misconstrue, I haven't done any of the actual development on this acoustic code .
See Jerome's tree if you want to see where this all started. A few others have cloned his tree and made some modifications. We're still working out the kinks. Perhaps it can help your port as well...
Like I said earlier, I am betting the userland stuff will work for you folks without a ton of changes (don't know for sure!). The kernel stuff for this new acoustic will need to be ported - our kernel will not work on your device.