Related
Ok, I'm posting this in its own thread as people seem to have missed my post earlier today as it got buried in the Crossbow Reloaded 1.7 thread:
I've uploaded a test rebuild (couldn't sleep last night and was up early this morning). This is version 1.7.1 . The differences to 1.7 are:
A lot of the compression I did in 1.7 has been removed
Adobe Reader Removed due to the compression on other things making the rom too big
AltTab added and is mapped to the Comm key (this should fix the problem with Voice command people complained about).
Now built with the Core Kitchen
A few other things that I don't remember now
People that have had the dialpad issues in the 1.7 release are what this is really aimed at. If 1.7 was working for you, then stick with that version (unless you need to have a flash "fix" ). I've flashed 1.7.1 to my phone and so far it seems fine, but I really haven't tested it much, so consider this a public Beta. [Edit... Been on my device all day today and so far no issues that I've seen, but then 1.7 was fine for me too...]
I reserve the right to pull this off of RapidShare if I find something I don't like or if others find the keypad issue still exists (I'll post if I do this). Please do NOT MIRROR this without my permission as this is NOT an official release but one I'm trying to see if it fixes the issues with 1.7 that some have had.
Download Link:
Crossbow Reloaded 1.7.1
Please post feedback in this thread. I want to see if the keypad issue is gone now (mainly).
.
The new version is brilliant. I'm loving it so far.
Thanks man.
Does it Have Pocket Outlook?
If it doesn't how do I add it back. Ta, Rin.
Wise choice with the kitchen lol
Thx for mentioning. It makes me proud to hear/read that
I hope it didn't gave you any more trouble.
Did you already started to modify it not to use default install ? Cos if you didn't i'd suggest to wait a day at most ..i am trying to rebuild it. That thing bothers me too.
Running smooth!
I really liked the reloaded 1.5, was running the reloaded 1.7 version, liked it a lot exept the comm button and some OS stalls.
Flashing the 1.7.1 version now and will let you know how it's going in this threath. Also curiuos how the core kitchen is doing
After 30 minutes flashing I killed the shelltool. Since the phone seems stuck I gave it a soft reset and it booted with WM6 splash screen referring to farias rom. Gave it a factory reset and it seems working. Don't have acrobat so I asume it's the 1.7.1 version. Will start working on it now.
Weatherpanel, cybercom voice dialing, tomtom all running smooth. Some little tweaks (I changed under HKLM\SoftwareMicrosoft\Bluetooth\A2DP\Settings the key "Bitpool" and MaxSupportedBitPool to "40" decimal for my Jabra 620) and no problems sofar. Now do some VOIP settings. It never worked, now it's time to get it working on my private asterisk
Ok, working on with the new Beta rom I had some stalls (Three). Green light blinking only no responsive power button. After a reset I repeated my actions before the stalls only I couldn't reproduce it. Since about twelve hours of usage no problems
Mirror the download, please
Can someone mirror the download to some where else? Rapidshare is SUCK.
Flashed it 30 minutes age, installing soft right now, and everything seems to be ok. I had problems with dial pad in 1.7, but in this its ok. Will post in case of any issues
A new 100mbit mirror
Yo mfrazzz, got you a mirror again:
Mirror
TheWizzard2203 said:
Yo mfrazzz, got you a mirror again:
Mirror
Click to expand...
Click to collapse
Thanks for that mirror, but nobody else mirror this for now. I'll wait a day or so for reports of problems then decide if its the final version.
If you flash this and it works fine, please post that. If there are problems with the rom, please post those.
testing new version... no probls found...
Same here, just flashed it and testing now. So far the dialpad issue looks to be resolved. Not certain yet, will post problems that occur.
Nice rom
fast and easy to use
BUT...
I think i have a pb with my battery
lose 5% by hour ... is it normal?
ps : but all is perfect
I just had time to come back to XDA since I loaded CBR 1.5.
I have had the dialpad issues in 1.5 and thought it was just additional software I added. The device didn't lock up and all other functions worked.
The solution I found that worked was to pull the battery for one minute, then do a soft reset once it booted up.
Will load 1.7.1 tonight.
Thanks and keep up the good work!!!
ndoeberlein said:
I have had the dialpad issues in 1.5 and thought it was just additional software I added. The device didn't lock up and all other functions worked.
Click to expand...
Click to collapse
You had dialpad issues with 1.5??? Nobody has ever reported that (that I remember), and 1.7.1 is directly built off of 1.5 (thats before I used compression or anything. 1.7.1 does use compression on a few things, but very minimal compared to what I did with 1.7). While there were definetly dial pad issues in 1.7, I think if you did have dialpad issues in 1.5, it truely was due to 3rd party apps, or tweaks on your phone.
Please report back how 1.7.1 works for you. Overall I'm happy with it, but I felt 1.7 was actually a faster rom than this one (there are times this one feels slightly slugish in places and I may have to turn on overclocking (where I never considered overclocking 1.7)).
So far 1.7.1 is looking good (but so did 1.7 for about 24 hours). I may make this an official release as is if I don't hear anything before tomorrow evening.
kwanice said:
Nice rom
fast and easy to use
BUT...
I think i have a pb with my battery
lose 5% by hour ... is it normal?
ps : but all is perfect
Click to expand...
Click to collapse
I am running version 1.7 but the battery life on this build is superb. Today I only made one call, left push E-Mail on a turned WiFi on and off a few times. After 13 hours I was down to 98% ! This is with a one month old battery.
How old is your battery ? Mine started to fail after 14 months.
i have not had any problems yet. It's great! will let you know a few days if I ran into any problems.
Voice command issue is it gone?
Hi mfrazzz,
Thanks again for another new version.In the previous version I reported one issue with voice command. Is that resolved in this version.
Issue was the voice command could not be activated using bluetooth headset. I have seen the keypad issue in 1.7 and sometime few error messages as well.
banerjeez said:
Hi mfrazzz,
Thanks again for another new version.In the previous version I reported one issue with voice command. Is that resolved in this version.
Issue was the voice command could not be activated using bluetooth headset. I have seen the keypad issue in 1.7 and sometime few error messages as well.
Click to expand...
Click to collapse
There was no issue with Voice Command and BlueTooth headset in 1.7 that I know of. I have a Plantronics Voyager 510 BT headset and a Bluespoon Spider stereo (A2DP) BT headset, and both pair up fine, and both control Voice Command fine for me. I know others using 1.7 and BT headsets worked fine with Voice Command for them also. It could be an issue with your headset and WM6, 3rd party software, or something else.
The only Voice Command issue I know of in 1.7 was that there was a button mapped by default that wouldn't work properly. I fixed that so that the Voice button (Button 4, upper right side of phone) now maps to AltTab app. AFter you install Voice Command it will map to your Messages button (button 1), but thats how Microsoft installs it, not my doing. You can then redo the buttons in Settings > Buttons and you are good to go (although I really like AltTab now, so I left it on Button 4 and only use Voice Command via my BT headset).
i had problems with 1.7...in that i the dialpad keys disappeared after first flash. i did a clear storage (1234, etc) and the dialpad came up. flashed this version (downgraded to official t-mobile 2.26, as I always do first) and i don't seem to have the same problem. everything was in working order the first time around. the rom actually feels a bit faster than 1.7. thx.
monkey_knight said:
i had problems with 1.7...in that i the dialpad keys disappeared after first flash. i did a clear storage (1234, etc) and the dialpad came up. flashed this version (downgraded to official t-mobile 2.26, as I always do first) and i don't seem to have the same problem. everything was in working order the first time around. the rom actually feels a bit faster than 1.7. thx.
Click to expand...
Click to collapse
if I wanna flash to the official t-mobile rom first can I use the rom program of t-mobile itself?
RUU_Prodigy_2210205_22102108_021911_TMO_NL_DUT_Ship.exe is my default rom I think
Hi,
Is anybody else experiencing issues with losing sound on their phone? I have been experiencing this on a number of different roms and initially put it down to an incompatible radio, but I have sinced flashed back to one of Dutty's roms (including radio) and it happened again. I have now flashed back to the stock bootloader and HTC rom and it has happened again!
I am at a bit of a loss now - am in the process of hard resetting my phone to see if it happens on a bare device as I had a number of apps installed although none of them had caused this problem before that I am aware.
Would be interesting to know if anyone else is getting this - don't know if its possible that any of the recent radio/rom releases could have done something permanently damaging to cause this. Will be sending mine back to HTC if it happens again, unless someone identifies a fix?!?
Cheers!
captainsensible2002 said:
Hi,
Is anybody else experiencing issues with losing sound on their phone? I have been experiencing this on a number of different roms and initially put it down to an incompatible radio, but I have sinced flashed back to one of Dutty's roms (including radio) and it happened again. I have now flashed back to the stock bootloader and HTC rom and it has happened again!
I am at a bit of a loss now - am in the process of hard resetting my phone to see if it happens on a bare device as I had a number of apps installed although none of them had caused this problem before that I am aware.
Would be interesting to know if anyone else is getting this - don't know if its possible that any of the recent radio/rom releases could have done something permanently damaging to cause this. Will be sending mine back to HTC if it happens again, unless someone identifies a fix?!?
Cheers!
Click to expand...
Click to collapse
happened to me yesterday. i had to hard reset and my phone still isn't customized 24hrs later.
Do you remember what apps you had installed?
I'm starting to think all of this has something to do with MSVC.
well i have consistently been using version 19209 whilst having these problems. Going to try 17913 again and see how that goes.
Mine too
I've been getting this alot lately, too. I think it's either MS VC or S2U2 1.01, or a combination of them.
I've done the same thing, flashed multiple ROMS and radios, but I've stayed in the WM6.1 family. I was running Confused Stu's Vista 1.2 forever and it suddenly started doing that - loosing sound. I went to 1.3 and then over to a Dutty build, and have now settled on L26_WM6.1_PROV4_(3.51.502.0_WWE)_Multimedia... This time I went slow and only loaded a few apps at a time. I thought it was Calendar+... But I don't have that on here yet.
It seems like it ran fine until I put S2U2 on here, but like I say, I use MS VC to announce everything so maybe it's some action there that didn't happen until after I put s2u2 on there, or maybe coincidence.
I wonder if anyone else is seeing this? I think I'll start over without S2U2 - even tho it rocks! - and chill a week.
Do you use S2U2? Do you use Caller ID in S2U2? How about slide 2 answer, slide 2 end key options? What about blank screen on talk option?
Thanks,
H
s2u2 v1.01 could be the culprit as i have been using it. After slowly reloading apps this morning sound had gone again, and one of the last to go on was s2u2. I don't think MSVC is the problem as it has never done it before plus its cooked into a lot of new roms, whereas s2u2 isn't. Am going to uninstall s2u2 and see what happens. It was one of the last things I put on and sound had been stable before that.
Im getting this issue as well, what radio are you guys running just out of interest, im running duttys 6.1 build 19199 with radio 1.65.14.06
I haved the same problem and resolve it by flash ing TNT 19202 Series PRO with radio 1.65.14.06. Best regards.
Well, the issue came back on the stock rom when I bit the bullet and installed a slightly older version of S2U2 (0.99p)!
I have now reflashed Hard-SPL and the latest Dutty Rom (with MSVC included) and have resisted putting S2U2 on and so far, so good!!
Hey, Zaf, do you run S2U2 or MS VC?
I flashed back to the AT&T Tilt stock ROM (downloaded from HTC web site, incl the radio) and reloaded S2U2 1.01 and MS VC. I lost sound within a couple of hours.
I did a hard reset and have not installed EITHER... I plan to run for a day like this, then put MS VC back on for the weekend, and then S2U2 after that.
I think it's S2U2 and I think it's been around since .99p. But I think 1.01 is worse than .99p or 1.0.
Well, at least we're narrowing down the variables!
Hey, everyone - watch http://forum.xda-developers.com/showthread.php?t=390977
for a similar discussion.
I flashed TNT 19202 Pro thus morning and the sound died few hours later again... Don't use S2U2. I posted more here - http://forum.xda-developers.com/showpost.php?p=2207600&postcount=18
I have lost sound 3 times, it is only through the speaker though, my bluetooth headset continues to work. Once I flashed a new rom to fix it, the other time it fixed itself over a few hours. The third time is happening now!
I have never used S2U so it can't be that. Have been using Dutty's roms, my radio is currently 1.58.16.27.
are we talking about sound in calls, if so i have been experiencing calls dropping and other people can hear me fine but then it suddenly goes quiet for the other caller and they can barely hear me? is this a fault with my kaiser or to do with flashing with custom ROMs.
I think we need to be very clear here what the symptoms are of a specific problem.
My symptoms were that sound would initially be ok after flashing a new ROM (whether it had MSVC cooked in or not) and then I would go through the process of installing my 'regular' apps which has always included S2U2.
Then, at some point after doing this, all sound would disappear - from the device and also during calls (interestingly, during calls, the other party could not hear me either).
I cannot explain for one moment the issues that people who don't use MSVC/S2U2 - some of these might be explainable by radio issues but I am not an expert by any means so would not be prepared to blame that!
All I know for certain is that up until recently I could use MSVC 1.6 build 17913 alongside S2U2 0.99 with NO issues at all - this is why I think that MSVC 19209 combined with S2U2 is the reason.
One other thing, I have not tried S2U2 on its own, without using MSVC, mainly because I am fed up with flashing! Perhaps someone else could confirm or deny if this has caused problems?!?
Yes, my symptoms are EXACTLY as the captain describes in his post... Everything fine for a little while after flashing, but soon after I get all my apps reloaded I call someone, or someone calls me, and there is no sound. No audio at all from the speaker, bluetooth, or in-call speaker. The caller can't hear me, either. I have to soft reset or power cycle to get sound back but it doesn't last long.
All day I've run with the AT&T stock tilt ROM from HTC's web site, still hard SPL'd, and I did not load MSVC, S2U2, or HTC Home yet.
R 1.27.14.09
G 22.45.88.07H
D 1.62.00.00
I have run all day with no sound problems. I am now about to plunge and I think I'll put MSVC on there first and run another day, only because on a whole it's cooler than S2U2. Lets see what tomorrow brings.
Hey, I just found this one: http://forum.xda-developers.com/showthread.php?t=391262
I am using an older build of MSVC... I grabbed the latest build and will give that a shot first. What build are you using? I WAS using 1.6.17913 but aparently it is old. I just grabbed 1.6.19209
Its interesting that you're seeing the issue with the older build of MSVC as I never had it with that build, although I can't remember if I used that build with the latest version of S2U2.
My phone has gone a whole night now with no issues without S2U2 installed, so I think that proves there is a link. Not sure if I can be bothered trying S2U2 without MSVC as, like you, I prefer having MSVC over S2U2.
What is also interesting is that there has not been much (one post I think) mention of this on the S2U2 thread. I may bring it up...
The trouble is, in 6 weeks of trying to deal with the problem by re-flashing ROMs and radios, I would still have the issue. Even though I never install MSVC nor S2U2. I even had the problem on a "clean" setup - just the ROM, I setup Internet connection, ActiveSync wireless Exchange and Note2Self - that's it nothing else. And I would lose sound within 3 to 20 hours with this setup. That's the cleanest setup I could get - I don't need my phone if I don't have Note2Self )
Just saw another of the symptoms... Another thing it would do would be to just crash after a call. So hitting END leaves the screen stuck with whatever's on it, and no way to get off that dialer screen. OK doesn't work, though when I push my VC button I hear it beep. This just happened after a call.
Anyway, I did a power cycle and it's back now. But I do not have S2U2 on here, though the MS VC lady is getting a real workout today... Anyway, sergeb will still tell us that neither app matters, anyway.
Uggh. Still resisting urge to put S2U2 on here.
FYI, there is an issue with pretty much all ICS ROMs and the BT stack included in them. I have a brand new, top of the line Jawbone BT that supports everything, works flawlessly in Cyanogen and non-ICS ROMs, but will barely work in ICS.
Basically, after a reboot, it connects and says Connected (no media), then switches to Connected. Everything works fine until I disconnect and reconnect again.
After that, it will work for only voice calls. Media will always go out the speaker. I have tried everything to fix it to no avail. The only resolution to get A2DP media streaming back is to reboot.
When it happens, the media checkbox is still there and checked, but it doesn't work. I switched back to HyperSensation (Cyanogen) and everything works as it is supposed to.
Apparently ICS bluetooth works fine for some BT headsets and not others. This also seems to be an ongoing problem for other phones as well, even non-ICS.
I am not well versed in reading the debug logs, but if anyone is interested I can post them here, provided they tell me which ones they want.
I'm having troubles to. My problem is I cannot start a call via the Bluetooth Dial button on my radio. It's as if the phone doesn't even recognize that you are pressing the button. Tried installing Vlingo, but the prompt doesn't even work anymore.
The old solution was to install the Voice_dialer.apk...but that doesn't seem to be compat either
I can confirm the issue with the virtuous ICS as well. I have bt stuff from Jawbones to BlueAnt's and all have the same issue. Prior to this was the issue of cutting out and now it's the off/on bt streaming. To "fix" the issue, is to reboot. Annoying yes. But ICS is still so sexy
I've got the same problem, ROM Elegancia ICS 1.0.6 and 1.1.0
After pairing with bluetooth headset, first time I play music everything is ok. after re-connecting, music controls works ok, but sound is thru phone's speakear not thru the headset.
After rebooting the phone the situation is the same- first connection everythings ok, another ones not.
Checked with SE MW600, Jabra extreme and car's bluetooth.
The problem occurs even with clear installation (before I restore backups).
Still can not find solution so I got back to GB.
So its not just me! I can confirm that my Beats Wireless acts exactly like described.. And with a reboot fixing it again!
I think the devs here might be able to fix it, but its properly not going to be an importent issue to fix.. Fingers crossed for a fix, or maybe the future leaks will have it done!
Sendt fra min HTC Sensation Z710e med Tapatalk
ftblstr2319 said:
I'm having troubles to. My problem is I cannot start a call via the Bluetooth Dial button on my radio. It's as if the phone doesn't even recognize that you are pressing the button. Tried installing Vlingo, but the prompt doesn't even work anymore.
The old solution was to install the Voice_dialer.apk...but that doesn't seem to be compat either
Click to expand...
Click to collapse
Vlingo has always been problematic for me... My solution (worked on ICS too) was to get it working on an older ROM (not sure which one anymore) then use titanium backup and back up APP+DATA on a ROM that it is working on. Then, restore APP+DATA on the new ROM.
The first time you hit the button on your headset it will ask you what app you want to use for voice dialing and give you Vlingo, Vlingo InCar, or Voice Search. Choose Vlingo and check the box to make it default and you are good to go.
Just make sure after you get it working on the new ROM to back it up again... then the next time you switch ROMs, restore whatever the latest backup is. I am not sure what it changes, but I have been through Cyanogen, all of the ARHD versions, all of the InsertCoin versions, and a few others (I can never make up my mind on ROMs) and this trick has worked in all of them.
IMPORTANT: Make sure in Titanium Backup to uncheck the option to restore system libraries in ROM (that can cause issues going between major versions of android), and make sure toenable the features in Titanium Backup for attempting to migrate data.
I also get the same issue when I try to connect my MW-600 with ARHD ICS 6.0.2.
Can anyone help?
You guys who just have to reboot your phone are getting off easy. When I lose Audio Streaming to my car head unit, I have to delete the device and re-pair it to my phone after a reboot.
Same here with mw600 on virtuous Inquisition 2.0.1. Only first connection plays music through headset.
I am sure that first 4.0.1 beta base was not affected. This bug came with 4.0.3
Sent from my HTC Sensation using Tapatalk
dante-fu said:
Same here with mw600 on virtuous Inquisition 2.0.1. Only first connection plays music through headset.
I am sure that first 4.0.1 beta base was not affected. This bug came with 4.0.3
Sent from my HTC Sensation using Tapatalk
Click to expand...
Click to collapse
really??.. Im gonna try an old backup then.
Edit:
Backup was removed sadly.. :/ cant test it, but maybe someone else can?
Well, the ROMs are still there to download
With 4.0.1 I was on radio version 10.59. I am not expert on radios and RILs but I guess these things affect also BT performance. Right?
Sent from my HTC Sensation using Tapatalk
Shidapu said:
really??.. Im gonna try an old backup then.
Edit:
Backup was removed sadly.. :/ cant test it, but maybe someone else can?
Click to expand...
Click to collapse
I reverted back to the virtuous 4.0.1 build from the most recent (having the new fw and radio) and has fixed the Bluetooth issue. Now I just have to live with messed up signal bars and a browser that randomly exits.
Sent from my HTC Sensation using xda premium
Hi,
Reporting this BT issue for me (SGS 2 with ICS 4.0.3, XXLP2 that can be found on XDA, originally from samfirmware):
I try to send files from my laptop to my SGS 2, 1 at a time and the transfer will suddendly halt some of the way through and ICS looks like it's rebooting but it's actually not, I mean not a full proper reboot; the phone does not switch off, the boot anim plays as if restarting, first BT is off then the icon come up in the top bar...
Hopefully, the Simple & Clean, ICS version, is round the corner ;o)
beng
using arhd 6.1.1 here on sensation XE with SE mw600 headset, no issues, calls and media working as normal
BT connectivity seems to be fixed in the latest leaked ICS + Sense RUU.
Is the sensation supposed to support any other remote control features than pause and play over BT?
I can confirm that on my Galaxy s2 using the 'official' ICS rom released yesterday still causes my phone to reboot.
This happens when bluetooth is paired with my car stereo and streaming audio or voice calls. It causes a reboot, usually happens after 10-15 minutes.
Never happened on gingerbread of any version. And has happened on all versions of ICS leading up to 'official' release.
I can confirm that bluetooth will cut off and be off completely quite randomly while listening to music or Pandora.
Only a reboot gets bluetooth to turn back on.
I have experienced this on two Motorola S9-HD headsets on various ICS roms
Sent from my HTC Sensation Z710e using Tapatalk
TL;DR
G2X w/ CM7 Bluetooth Streaming media text (track info) works, but calling doesn't
G2X w/ 21Y Bluetooth calling works, but streaming media text doesn't.
Is there a way to fix one or the other?
Hello,
I have a T-Mobile G2X and use a base install of CM7 with gapps.
I recently purchased a Pioneer FH-X700BT stereo receiver for my vehicle. The nice gentleman who installed it briefly went over the features including the bluetooth. When using the bluetooth media streaming it worked superbly. Whether I used the device music player, Google Music or Akimbo (for my audiobooks) the song track / artist info is displayed. However when he attempted to use the bluetooth calling features there was just hissing and static. He wasn't able to figure out why this was and showed me how it functioned correctly with his blackberry phone. I figured: "well crap, maybe there is finally a reason not to use CM7 on my phone."
After returning home I reverted my phone back to a backup of 21Y. Bluetooth calling works great, but now my media info is no longer displayed. Back and forth, same problems.
After searching on XDA I came across the New Baseband Fix (http://forum.xda-developers.com/showthread.php?t=1776843) thinking it might be related, but alas no such luck.
It seems I can have bluetooth calling or bluetooth media info, but I would like both (even if I have to use stock). Is there an app that will make sure my track info is streamed while using stock? Is there a ROM that has both bluetooth calling and track info streaming?
Thank you for your assistance,
BigRedOgre
Yes this is a problem with the new baseband (March 2012) I don't think there's a fix for it yet. There's a few methods to downgrade back to the old baseband where it was working but it's sorta hit or miss. A lot of people have trouble getting it to work.
TwitchyEye said:
Yes this is a problem with the new baseband (March 2012) I don't think there's a fix for it yet. There's a few methods to downgrade back to the old baseband where it was working but it's sorta hit or miss. A lot of people have trouble getting it to work.
Click to expand...
Click to collapse
TwitchyEye,
Yes, I found that in my searches; concerning the bluetooth calling. I didn't find anything on the streaming media info. Are they both related to the baseband?
Regards,
BigRedOgre
I'm not really sure about the streaming. My understanding is it was working fine, but I haven't tried it myself. Surely someone around here has personal experience with that end of it.
TwitchyEye said:
I'm not really sure about the streaming. My understanding is it was working fine, but I haven't tried it myself. Surely someone around here has personal experience with that end of it.
Click to expand...
Click to collapse
Yeah, New baseband with CM7 = no call audio but media should work. T-Mobile 2.3.4 stock = both working.
If you want CM7 and both working you need to downgrade the baseband.
-- The noob says:
It's alive!
(Adopted from Robot Chicken for the g2x.)
this is the ONLY issue I have with my phone on new baseband with CM7. Especially since my car has built in bluetooth calling. I misses it =(
mansa_noob said:
Yeah, New baseband with CM7 = no call audio but media should work. T-Mobile 2.3.4 stock = both working.
If you want CM7 and both working you need to downgrade the baseband.
-- The noob says:
It's alive!
(Adopted from Robot Chicken for the g2x.)
Click to expand...
Click to collapse
but you have to go with an older version of CM7 right? 7.2 didn't work for me with the new baseband. no audio.
jblah said:
but you have to go with an older version of CM7 right? 7.2 didn't work for me with the new baseband. no audio.
Click to expand...
Click to collapse
Not quite. CM7 with new baseband requires flashing new baseband zip file (search the forum), but you would have just media over Bluetooth, not call audio over it, however call audio over phone and speaker should work.
-- The noob says:
It's alive!
(Adopted from Robot Chicken for the g2x.)
Man I wish I were capable of cooking a ROM myself and stripping out the parts of other ROMs that work and compiling them together.
I'm on Sprint, xt897c CDMA, I've tried stock/rooted, CM10.1 stable, CM10.2 M snapshot, various CM10.x nightlies, and a couple of the latest PACman nightlies. Every single one of them has things working that others don't, and something not working that I can't live without:
Stock/rooted - need a good/easy way to wifi tether to my Nexus 7 tablet and laptop. Wifi tether app in the play store doesn't work like it does on other phones I've had. JB-style quick settings and notification widgets would be nice too, but mainly this is missing the wifi tether. I could live with it if it had that. However I really want to be running something CM-based...
CM10.1 - Everything runs great on the stable build - its fast, stable, has all the features I want, but there's a problem with the phone audio. My phone first and foremost needs a stable phone. There's a high-pitched whine/hiss in both the speaker and mic that makes phone calls annoy the far end, give me a headache, and makes speaker phone all but unusable. Its also there when recording videos and it stays with the video when its transferred off the phone.
CM10.2 - Same issue as above, plus it hangs on bootloader after the first reboot. Every version I've tried.
PACman - Phone calls sound great - no audio issues. All the features I want. But it's not stable. If I'm listening to music in Apollo and switch to Maps, Apollo just terminates (not FC, just closes like the memory manager killed it or something). Same thing with many other apps (Strava recording segments, etc.). Also the GPS lock is terrible or non-existent.
Ideally I'd like to solve the audio issue with CM10.1 or that and the reboot hang on 10.2. If anyone knows of fixes for these I'd be immensely grateful. I've seen others refer to them but no concrete confirmation or a fix mentioned...
/rant
Try Carbon, try AOKP... try Slimbean. What else... PA? I can't think of any others which have been ported to our device.
Try other ROM's, and I can assure you the ROM's will get better with time - although it's odd you have a high pitched whine in CM but not PAC. I've heard some report that whine, and I was under the impression that all the aftermarket/custom ROM's suffered from that issue.
Either way, CM11 is shaping up to be pretty solid - although I have had a few random reboots, not sure what the issue there was. Mostly when using Google Music in airplane mode/no service areas.
@cmags: As far as I was able to reproduce it, the high pitch whine/buzz was caused by MICBIAS CAPLESS Switch enabled and I've addressed this issue for CM-10.2 branch here: http://review.cyanogenmod.org/51949
I have no issues using speaker phone (I'm running cm-10.2 and cm-11.0 on my two Qs).
Regarding the noise in the high frequency range in camcorder recordings, I'm still not sure about the cause nor a solution for it. (I mean the pure noise, not the whine here).
Regarding the hang after first reboot, I'm not able to reproduce it and the logs from users I've seen so far were not very helpful.
I suspect that it may be caused by the timing of the mounting of internal partitions, but I'm not sure yet.
I'd welcome /proc/last_kmsg captured in recovery after such failed boot.
Thanks for the helpful replies fellas. @kabaldan I'll test out your latest branch and grab logs if I experience the issue.
Sent from my XT897 using Tapatalk
The latest skrilax build of CM10.2 seems to have resolved the audio issue. I was even able to restore my CM10.1 nandroid, flash 10.2 over the top (along with new gapps) and keep my data/settings. Thanks guys for the help!