[Q]Programming Radio - HD2 Windows Mobile 6.5 Themes and Apps

I am wondering if someone else here is familiar with programming the radio on the leo. I spent some time in finding out about how to use the HtcFm.dll and FmRadioSdk.dll, but I am stuck now.
Especially the use of FmRadioSdk.dll seems to acknowledge all my requests (by calling my callback function and responding as expected). Unfortunately, I hear - nothing .
Is there something I might have forgotten ? Is there something special I need to do in order to hear something ?

leihen said:
I am wondering if someone else here is familiar with programming the radio on the leo. I spent some time in finding out about how to use the HtcFm.dll and FmRadioSdk.dll, but I am stuck now.
Especially the use of FmRadioSdk.dll seems to acknowledge all my requests (by calling my callback function and responding as expected). Unfortunately, I hear - nothing .
Is there something I might have forgotten ? Is there something special I need to do in order to hear something ?
Click to expand...
Click to collapse
flywhc has done great work on a couple of devices, and is researching this too, but he doesnt have a device. Maybe you both could solve the riddle? Here's his thread

Related

Can't turn on the bluetooth

hello,
unfortunately i cannot turn on the bluetooth from comm manager, it turns on and after 1 second is off again.
any solution for this problem?
thanks.
I have had this problem before and unfortunately am having it again. Only solution I have ever found for this is a hard reset and then reinstalling all your apps. If you try to restore from a backup from Sprite Backup, for instance, the problem remains. This would lead me to believe that it's a setting or a registry issue somewhere but I haven't been able to locate exactly what would be causing it and don't know enough about programming in WM to write something to figure it out.
Not a great answer but there it is.
db
MegaHz said:
hello,
unfortunately i cannot turn on the bluetooth from comm manager, it turns on and after 1 second is off again.
any solution for this problem?
thanks.
Click to expand...
Click to collapse
Hi, I have a Uk version of the touch cruise and I have the same problem. I just did a hard reset but the problem remains. Turning bluetooth on is impossible. It just try's to turn it on and shuts it off immediately.
Maybe it has something to do with GPRS? I am always connected to the internet. I tried to disconnect but then bluetooth still doesn't work. Can anyone help? Thnx!
No one has a clue?
I had this prob with bluetooth and wifi following the use of wmwifirouter- after hard reset and no wmwifi all goes well...
On a French SFR rom
any other idea?
Same problem... beginning to wish I'd gone all Apple and bought an iPhone. Anyway.... To trun it on, I had to go to Comm Manager>Settings>Bluetooth>Mode>Turn on Bluetooth. That worked despite the Comm Manager still showing Bluetooth as "off".
It only connects 1/2 the time to my headset or handsfree in the car
Otherwise, the phone crashes only once a day! Great! Thanks!
ok, great to see more people having the same problem but i hope that someone has a sollution...
When I try to turn bluetooth on in the communications settings i get a message saying there is a hardware error! :S
Ohw btw, I'm not using any router programs or other and my WIFI works fine.
has anybody of you having this problem tried to change to another rom?
if yes? did this worked?
any news on this?
No news, I don't want to try for a different rom because i don't think it will change anything. It just seems like its a faulty device which is a real shame. I've already contacted the place where i bought it and see if i can get a new one.
I also have problems with my microphone during calls, photo camera does often not work and the touchpad reacts very slowly to my touches. Very annoying!!!!
Yup, am returning mine to HTC aswell. Not even sure I want it back. WiFi stopped working too, and then it stopped receiving text messages, and everyone said they couldn't hear me when I called them. Great
Some of you guys got a bad device, there are thousands out there working properly.
If some of you guys flashed a newer Radio, the one form the test-ROM, then this is your problem.
And some of you guys have a quite gay branded ROM (slow responsiveness of touchpad). The original HTC ROM on the FTP and even more so a cooked ROM would solve alot of your problems. But be aware, flashing without having a backup ready is going to void your warranty if you want to exchange it having a custom/non-original ROM on the device.
What's up Schaggo
I am experiencing the same problem these gentlemen are mentioning and my ROM is not gay or lesbian. It is the original one.
TC is my 7th HTC device and I can see the quality of the ROMs decreasing a lot on every new device. I feel like HTC needs a real competitor to move up its arse quicker.
All I can say is that it really annoys me to hard reset this [email protected] everytime I "accidentally" use a native feature called Flight Mode. By bluetooth seems to fly away and never get back.
Lots of time the GPRS settings have to be reconfigured too. Some people I know have problems with GMail IMAP4 accounts when sending messages after some time. I never had this problem on my Kaiser neither on my Niki.
The lack of a video driver really is an egg on our faces, because I can't believe my ole Qtek 9100 responds quicker than these "all the bells and whistles" Qualcomm 7200 super-duper geared up devices.
So, if you feel like not contributing, please do not mess around.
Your signature tells me you are a wise man, but your comments show me otherway.
-Feaps
PB of BT still there with custom rom
MegaHz said:
has anybody of you having this problem tried to change to another rom?
if yes? did this worked?
Click to expand...
Click to collapse
Hi
I've tried many custom rom and the PB continue. "PB with the hardware oh BT".
Hard reset doent change anything.
my initial rom (SFR France) was working
custom rom (blackwidow + Bepe 058) are buging...
nedd some help !
Thanks alot for that input feaps. I guess I have to clarify a little bit.
My answer was supposed to be pointing in different directions. The first and general information I tried to contribute was, that it is not a common Polaris problem to have a broken Bluetooth unit. Which doesn't help at all to ppl affected, but it should tell them, that they probably got a bad device and should exchange it first before blameing htc in general and shouting for an iPhone.
It only was partially directed at specific persons. At madinga for example: did you try hardresetting your device? It could be a corruption in your system which causes all those problems. I doubt it though, if you suffer the loss of so many functions at the same time I suspect the mainboard to be broken. But nonetheless, hardreset it, see if its working, BEFORE you put your backup back on the device again since that could restore the corruption. If it doesnt work, exchange your unit, I hope you'll get a working one back.
My second line was directed at all people which have overwritten their original Radio with the 1.58.25.14 originating from the HTC Test ROM which can be found on the ftp server. The Bluetooth part of that Radio is flawed and leads to the problems described in this thread. I quite nicely pointed that out and told people where to have a look before shouting around. I do know that because I tried it myself and couldnt get my Bluetooth devices working. Once I flashed the original Radio back, my BT problems were gone.
And my third line - in which I may chose the wrong words, 'gay' for example - holds information targeted at people with for example the branded french SFR ROM or the original HTC french ROM. The SFR ROM is just horribly branded and if you go through the threads here you'll find people complaining about problems which then turn out to be related to the ROM. The french HTC ROM is flawed as well, it has severe problems with the volume control. I don't exactly remember what it was, but it's a flawed ROM, thats for sure. The German o2 ROM isnt flawless either, I know that because I originally had that ROM. Once I flashed my orbit 2 with the original HTC WWE ROM, I found it to be working alot better and smoother than with the o2 ROM originally provided. And this is where my last line comes into play: if you suffer problems related to your currently flashed ROM, they could be diminished by flashing an alternative ROM. But if your device is broken, and I personally and strongly believe that everybody fooling around in this forum should be intelligent enough and able to determine the sense of my words, eg. if he/she suffers a ROM problem or if the device just simply is dead and take appropriate actions.
And now to your contribution feaps. I feel personally attacked by your words. Thats why I defended my words in all the paragraphs above. Trust me, I've had enough mobile devices of all sorts to know what it means to get a not working once. Its frustrating and makes you want to throw it out of the window. And being able to see the quality decrease over time is just another drop on a hot stone. I agree. But be honest, if your BT unit works and stopps working once you engage a software based function, the problem is software related, dont you think? As for the GPRS settings, I cant tell. Since I use a free ROM which has the wizard built in (o2 removed it from their ROM) I didnt switch my SIM and the configuration worked, automatically and every single time. And I do use IMAP as well on my personal E-Mail account. Until now I didnt run across any problems, so I cant give you any feedback on that either.
So rethink again if I mess around or not or if I actually try to contribute and help the freshmen, coming into this forum and flashing whatever they find and breaking their devices. And recommending to flash the original HTC ROM, which should be/is the base for everything floating around, breaking your devices, is a serious input to everybody.
Edit: I forgot to add, pointed at nooms, there are cooked ROMs out there which stupidly have the new, flawed Radio baked in. Which Radio are you on? Try Start > Settings > Tab System > Device Information > Tab Version. Are you inadvertedly still on Radio 1.58.25.14 or back to (original) 1.58.21.23?
Hi everyone,
I agree with Schaggo completely. Most of the time problems have something to do with the software on the device. But I a not a tweaker like most of you guys, i've just bought my first (and hopefully not last) HTC phone. If i have problems of some kind, all i can do is reset the thing. A hard reset if necessary. I've done that many times. I can't change the software that comes standard and i don't think i should be the one who has to do that. Shouldnt HTC be doing that??
Anyway, Bluetooth keeps saying it has an hardware error. My radio version is a standard 1.58.21.23 but isnt finding any radiostations here in holland. Is it also broken? (sorry, i know, its a bit off topic)
You're right
schaggo said:
(...)
My answer was supposed to be pointing in different directions.
(...)
And now to your contribution feaps. I feel personally attacked by your words.
(...)
But be honest, if your BT unit works and stopps working once you engage a software based function, the problem is software related, dont you think?
(...)
As for the GPRS settings, I cant tell. Since I use a free ROM which has the wizard built in (o2 removed it from their ROM) I didnt switch my SIM and the configuration worked, automatically and every single time. And I do use IMAP as well on my personal E-Mail account. Until now I didnt run across any problems, so I cant give you any feedback on that either.
(...)
So rethink again if I mess around or not or if I actually try to contribute and help the freshmen, coming into this forum and flashing whatever they find and breaking their devices.
Click to expand...
Click to collapse
Well put. Sorry for being rude, but I keep seeing people offending others day after day in this forum that used to be high level; but that doesn't mean I should act the same way.
I totally misread you and please accept my apologies.
My ROM is: 1.25.405.1 WWE
ROM Date: 12/11/07
Radio Version: 1.58.21.23
Protocol Version: 25.65.30.04H
One thing I could notice is that HTC has a flaw in the Flush HKCU to Permanent Memory While Shutting Down. Some keys are not written.
One example is the MagiCall (an app I use) registration key. The software maker had to write a flush app for doing that. Another example is the Start>Settings>System>Error reporting. No matter what you chose, after a power cycle or a soft reset, it always go back to "Disable...".
I have, also, already tested the device after the hard reset with no extra apps on it. Same lame behavior on BT...
So, SW QA levels are really dropping fast on new HTC models. That is pretty bad.
But anyway, I have an open case with HTC and if I find something contributive I will toch base with this thread.
Once again, sorry for being rude.
Best,
-Feaps
Furio83 said:
Anyway, Bluetooth keeps saying it has an hardware error. My radio version is a standard 1.58.21.23 but isnt finding any radiostations here in holland. Is it also broken? (sorry, i know, its a bit off topic)
Click to expand...
Click to collapse
Then I guess you most probably got a bad unit. I guess the only solution at this time is an exchange.
The Radio-Firmware doesnt control the FM Radio btw The Radio-Firmware controls connections to the providers network, Wireless LAN and Bluetooth. But the FM Radio seems to be really bad in the Polaris, a lot of ppl I know complain about it.
feaps said:
please accept my apologies.
Click to expand...
Click to collapse
No problem dude! There is no need for such an excessive appology. We are in a Forum and people have different oppinions and I think its totally acceptable to shout at each other. I just wanted to express that I'm not in accord regarding your judgement of my post. But thanks a lot, I seriously really appreciate it!
Yes, your device seems pretty standard to me and the scenario you described logically made me think of a software error. But this seems very unlikely now. I'm out of ideas for the moment then, I guess you have to return or exchange it too.
You are perfectly right about the dropping SW QA though. You can notice the registry glitch in other areas as well: backlight timer always reset to 30 sec, and there are more settings all over the place which don't get saved properly.
Again, no problem, everybody lets be cool
Bluetooth doesn't turn on
I have the same problem. Did anyone find a solution?
Also camera fails to initialize, touch pad is sometimes very slow for initial reaction. I have NO added programs beyond manafacturer originals and have tried a number of hard resets. Doesn't help.
Jeremy

Phone not available after using GPRS/EDGE

Hi,
I'm not sure whether this problem was being solved/is resolved somewhere in this forum, but I wasn't able to find a solution to a problem I'm facing.
The thing is, that sometimes (not always) after I've browsed the web on my Vox, the phone seems not to be reachable on the network, i.e. if I try to call my mobile phone from another phone, I just get "The number you are calling is currently unavailable, please try again later".
This seems pretty confusing to me, since the phone shows that it is normally connected to a network and isn't reporting any kind of problems. But it really isn't able to receive a call...the only thing that works is to restart the phone.
Unfortunately, there's no way to tell if the phone is just fine and noone is trying to reach me, or it is stuck in this strange way...
Has anyone experienced simmilar behaviour/found a solution? Any help would be appreciated.
I'm running Dr. Gonzo's Rose v0.3 ROM by the way, but as far as I remember, it also was happening with other ROMs....
P.S.: I'm sorry for my poor english.
Hmm is there really noone else with these problems? Could it be a hardware problem then? Or anything specific for my Vox only?
I have this problem too - my vox sits mostly unused now

Can't answer my phone!!

OK, I've been having this problem for a good couple of months now. About half the time that someone calls me, when I hit the Talk button on my phone it just mutes the ringer and doesn't answer the phone. Usually I try the 'Slide to answer' deal, and that just slides over to Answer and still doesn't do anything. I know the actual button is fine, it works great, i've tested it over and over again. I've changed HardSPL, ROM's, Radio's, etc. and I still see the same issue. What is wrong?! or is anyone else having something similar at least?
So I guess no one else has this issue, at all, with any ROM, radio, etc.?! I guess there must be something wrong with my phone. That kind of sucks.
schwags said:
OK, I've been having this problem for a good couple of months now. About half the time that someone calls me, when I hit the Talk button on my phone it just mutes the ringer and doesn't answer the phone. Usually I try the 'Slide to answer' deal, and that just slides over to Answer and still doesn't do anything. I know the actual button is fine, it works great, i've tested it over and over again. I've changed HardSPL, ROM's, Radio's, etc. and I still see the same issue. What is wrong?! or is anyone else having something similar at least?
Click to expand...
Click to collapse
I had the same issue with my htc mogul. These suggestions worked, give it a try (i will NOT take credit for these great tips/found them by searching):
dial ##778#/EPST/Modem Settings, change the slot cycle index number to 1
and or if that didn't fix it...
Take a look at your HKLM/Comm/ConnMgr/Planner/Settings/SuspendResume
It is a multi-sz value and should be #777. If it shows anything like ~GPRS or
something containing GPRS, change it back to #777 and soft reset.
Once I changed it back to #777, I can answer the call immediately when data is on, time and time again. Prior to this, there was a significant delay.
Please backup your phone prior to making these changes...
Good luck...
montecristo1 said:
I had the same issue with my htc mogul. These suggestions worked, give it a try (i will NOT take credit for these great tips/found them by searching):
dial ##778#/EPST/Modem Settings, change the slot cycle index number to 1
and or if that didn't fix it...
Take a look at your HKLM/Comm/ConnMgr/Planner/Settings/SuspendResume
It is a multi-sz value and should be #777. If it shows anything like ~GPRS or
something containing GPRS, change it back to #777 and soft reset.
Once I changed it back to #777, I can answer the call immediately when data is on, time and time again. Prior to this, there was a significant delay.
Please backup your phone prior to making these changes...
Good luck...
Click to expand...
Click to collapse
Thanks for the help, I don't know if I believe any of that though. First of all, the # codes are carrier specific, I have AT&T, what's your service? These codes didn't work at all for me. Second of all, I mentioned that I've changed ROM's numerous times, along with Radios, etc. and I still have the same issue. Maybe this worked for you, but for me it doesn't. I've been trying some stuff recently, re-flashing SPL, hardSPL, Stock ROMs, and I'm hoping the problem goes away although I'm not that confident. I keep thinking it must be physical as my phone's "talk" button works perfect. Every time I try it it always responds appropriately, except when trying to answer a call. Beyond that, when it does screw up, it at least mute's the ringer, so I know it's responding somewhere.
I'm not sure what to do about this. Guess I'd better just wait it out for a TP2 and sell this one and forget about it. Could be due to bad blocks, I've had numerous problems in the past that I've been able to pretty much prove were a result of bad blocks in the phone's memory. Oh well, thanks for trying, although none of that works!!
I assume he has Sprint.
I have the same problem answering calls too, and I think it's because of the slidetoanswer dialer. I'm using xECK29x's 6.5 ROM.
rccola159 said:
I assume he has Sprint.
I have the same problem answering calls too, and I think it's because of the slidetoanswer dialer. I'm using xECK29x's 6.5 ROM.
Click to expand...
Click to collapse
Thanks for the input, I think I'm going to try a different dialer for a while and see if that solves the problem. I wouldn't be surprised if that's the issue.
While his codes may be different (I'm also with AT&T), he may be onto something... I have had the same issue, but after reading this post, I have been watching, and the times the phone prevents me from answering are when I have had some sort of data (browser, GPS, etc) open in another window.
My 2 cents FWIW
schwags said:
So I guess no one else has this issue, at all, with any ROM, radio, etc.?! I guess there must be something wrong with my phone. That kind of sucks.
Click to expand...
Click to collapse
I have an unlocked euro touch pro and cannot answer a call by touching the onscreen answer button. It will continue to ring tho. I have gotten in the habit of just using the hardware answer key. I've flashed numerous diff roms and all are this way, even the htc updated rom from their site. The only one that worked was the oem rom preloaded on the phone from factory. Not a big issue to me. I just deal with it.
Have this problem with energy's Roms. If you are on his 3.0 still go into Start>Tweaks>Advanced Config. Scroll down to Phone, Click on Phone Skin then Disable it. The setup of the call is different. Be sure to re enter you voicemail for it is erased when you disable the skin. Worked for me. No problems here. BTW you must understand that any Rom you flash will not be perfect!
I also have the same problem. And i to beleve its the new dialer thing. will try and change it, although i realy like the way you can search a contact with it. The other one is just a litte to small i feel. Anyway thanx for a good tip.
I'm also running into the same problem. I'll try disabling the phone skin to see how that works out.
Thanks everyone for your input!! I was a little scared to see no one answer this is at first, but now I can see this is a common problem. The dialer has to be the issue here, I've been running a standard dialer (not the phone canvas) for a couple days now and it's been perfect everytime.
montecristo1 said:
I had the same issue with my htc mogul. These suggestions worked, give it a try (i will NOT take credit for these great tips/found them by searching):
dial ##778#/EPST/Modem Settings, change the slot cycle index number to 1
and or if that didn't fix it...
Take a look at your HKLM/Comm/ConnMgr/Planner/Settings/SuspendResume
It is a multi-sz value and should be #777. If it shows anything like ~GPRS or
something containing GPRS, change it back to #777 and soft reset.
Once I changed it back to #777, I can answer the call immediately when data is on, time and time again. Prior to this, there was a significant delay.
Please backup your phone prior to making these changes...
Good luck...
Click to expand...
Click to collapse
Hey, it worked! I can't thank you enough, as this has been bugging the heck outa me. My slot cycle index was already set to 1, but my SuspendResume setting in the registry was "GPRS_bye_if_device_off". I had gotten to the point that I knew my problem was related to having a data connection going, but I had no idea where to go from there, and had no luck when searching the forums for a solution. Now my phone answers almost immediately, even whan I have a data connection going. Thanks again.

[Q] Tasker on MIUI/WajkIUI

Hi all.
Sorry if this is the wrong place to post, but this thread is regarding bugs on custom ROMs, so here I am.
A while back I switched from CM7 to WajkIUI, and I really have enjoyed this ROM since trying it. Recently however, I've noticed a couple of issues regarding MIUI/WajkIUI and Tasker. I've mentioned my problems in the relevant ROM thread here, and also on MIUIandroid.com, but nobody seems able/willing to help.
I have profiles configured within Tasker that will switch my phone to mute (Silent Mode) when I'm at work (based on WIFI near attribute, which is working fine). WajkIUI ROMs subsequent to 1.9.2 are unable to switch this, or indeed make any changes to volume.
I also have a profile that will switch on Bluetooth when I get an incoming call (using the Incoming Call option in Tasker). I've no idea when this stopped working, I'm on 1.9.2 at the moment, and it doesn't work here. I've tested the profile activates, and it does - but it doesn't switch on Bluetooth.
Finally, my third bug relates to the above, but not Tasker. If I switch Bluetooth on manually and pair with my headset - I can't get my headset to answer the call or to ring the last number (two things it has always done before).
Is there ANYONE who can help fix these? Are these issues solely on MIUI based ROMs, or does CM7 also have this issue - as I'm seriously considering switching back.
Thanks.
250+ views and not one response? Boy do I feel lonely now.
So, seeing as how nobody can offer any help on my actual problems - can someone give me a clue to how I go about decompiling a ROM to check the code out myself please?
simon211175 said:
250+ views and not one response? Boy do I feel lonely now.
So, seeing as how nobody can offer any help on my actual problems - can someone give me a clue to how I go about decompiling a ROM to check the code out myself please?
Click to expand...
Click to collapse
Try to update to 1.9.23
Will that work? I've tried all of them up to that, but every time had to downgrade due to the problems. I got fed up of installing a ROM only to have to uninstall it five minutes later.
simon211175 said:
Will that work? I've tried all of them up to that, but every time had to downgrade due to the problems. I got fed up of installing a ROM only to have to uninstall it five minutes later.
Click to expand...
Click to collapse
I think it's a bug in MIUI itself. If you check the app on market, there's a lot on Market who says so.
that's what I thought - I've an ignored thread in the bug forum on miuiandroid, hence my last question about decompiling the ROM so I can investigate myself.

[Q] Relay can't hear input from any bluetooth device, LAME

Am I the only Relay user having trouble using voice command thru bluetooth?
I'm running Cyanogenmod 10.2, on tmobile, and using google voice/talktone for calls.
On both bluetooth car kits I've tried (Blueant Commute and Kinivo BT450), things work fine (music, navigation, reading incoming texts, taking calls) until I try to voice command the phone thru the BT unit.
I've tried:
~ google now, voice search, voice dialer
~ turning on talkback (hate that constant reading of each page, AGHH!)
~ blueant app (does F%&&% all)
~ every tip on both gear's support pages
~ tmobile's support page (HA!)
~ even reverted back to stock (in case it was CM), and IT STILL SUCKED MY @**#&#$
I am ready to throw this POS phone against the nearest underpass..... if someone can solve this, I will send you thanks, and a present. Seriously.
(I appreciate all advice, but feedback from those who have this prob, or solved this prob are the most helpful. THX)
Epiclectic said:
Am I the only Relay user having trouble using voice command thru bluetooth?
I'm running Cyanogenmod 10.2, on tmobile, and using google voice/talktone for calls.
On both bluetooth car kits I've tried (Blueant Commute and Kinivo BT450), things work fine (music, navigation, reading incoming texts, taking calls) until I try to voice command the phone thru the BT unit.
I've tried:
~ google now, voice search, voice dialer
~ turning on talkback (hate that constant reading of each page, AGHH!)
~ blueant app (does F%&&% all)
~ every tip on both gear's support pages
~ tmobile's support page (HA!)
~ even reverted back to stock (in case it was CM), and IT STILL SUCKED MY @**#&#$
I am ready to throw this POS phone against the nearest underpass..... if someone can solve this, I will send you thanks, and a present. Seriously.
(I appreciate all advice, but feedback from those who have this prob, or solved this prob are the most helpful. THX)
Click to expand...
Click to collapse
We (TeamApexQ) have thrown ourselves against this wall a few times, to no avail. This is a known issue in our sound configuration. It really comes out of the fact that getting this to work would involve having a bluetooth device work in two separate profiles (A2DP for output, SCO for input) at once which is not a trivial or easy thing to implement. What we need are more logs of this issue, and probably some direct communication in IRC with a couple of testers to bang this one out.
Magamo said:
We (TeamApexQ) have thrown ourselves against this wall a few times, to no avail. This is a known issue in our sound configuration. It really comes out of the fact that getting this to work would involve having a bluetooth device work in two separate profiles (A2DP for output, SCO for input) at once which is not a trivial or easy thing to implement. What we need are more logs of this issue, and probably some direct communication in IRC with a couple of testers to bang this one out.
Click to expand...
Click to collapse
OK, so I'm not a retard. hehe, thanks for that, I was going crazy thinking it must be some setting I overlooked. Strange though, it still didn't work when I reverted to stock.... no? (THAT must be something I am doing wrong...)
After 6 months enjoying CM10 (big thumbs up for TeamApexQ!!), I can't bear the thought of trying to suffer thru stock rom....what's the closest rom to CM that has good bluetooth integration..?
Epiclectic said:
OK, so I'm not a retard. hehe, thanks for that, I was going crazy thinking it must be some setting I overlooked. Strange though, it still didn't work when I reverted to stock.... no? (THAT must be something I am doing wrong...)
After 6 months enjoying CM10 (big thumbs up for TeamApexQ!!), I can't bear the thought of trying to suffer thru stock rom....what's the closest rom to CM that has good bluetooth integration..?
Click to expand...
Click to collapse
Now, someone can correct me if I am wrong on this, but I believe all of the community images are using the same sound configuration that TeamApexQ has been developing since CM 10.1, so... None of them. Again, with some community assistance, logcats, testing, and patience we can fix it.
Magamo said:
Now, someone can correct me if I am wrong on this, but I believe all of the community images are using the same sound configuration that TeamApexQ has been developing since CM 10.1, so... None of them. Again, with some community assistance, logcats, testing, and patience we can fix it.
Click to expand...
Click to collapse
I thought I heard CM9 had working BT... if not, what can I do to help? how do I capture and send you the logs?
Epiclectic said:
I thought I heard CM9 had working BT... if not, what can I do to help? how do I capture and send you the logs?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1726238
Please, please, please issue a 'logcat -c' before doing this proceedure to capture a log of the issue, to clear the log, and to avoid having us to sift through every log your phone has taken since reboot.
Also, send us the contents of the 'dmesg' command after encountering the issue, just to rule out anything on the kernel side.

Categories

Resources