Develop Bugs

Is streaming/internet radio working on your Desire? (issue with wireless N patch?)

It's not working properly on mine, ever since I moved up to FroYo a couple of weeks ago.
Streaming works fine over 3G but if I use it on wi-fi, with the screen switched off, the music starts stuttering and eventually skips.
Thought it was an issue with the rom I was using, but I've tried three different ones (including one of the new ones from this afternoon) and I'm seeing the same issue.
Wi-fi policy is set to never sleep so it can't be that.
Could somebody test it out and let me know?
NB
It only happens on wi-fi
It only happens when the screen has been off for one-two minutes

Update, in the off-chance that somebody, somewhere has actually bothered to read this...
Flashed back to 2.1 and the issue was gone. Back to 2.2 and the issue is there again.
edited to remove pointless speculation. solution is on page 2.

why would you call HTC support, surely thats a job for the last.fm development team to work out.

Because I don't think it's an issue with last.fm. It apparently works fine on non-Sense phones, and even works fine with the earlier versions of HTC Sense.
Last.fm has permission to keep the phone awake, and it does so over 3G but not over wi-fi.
It doesn't really make sense unless the newer version of Sense is throttling the wi-fi when it goes into sleep mode and is not allowing last.fm to keep the phone awake.
Can't really verify that though... I might try to find another app that uses the wi-fi connection and see if it exhibits the same behaviour when the screen is off.
edit: just checked with the speedtest.net app and switching the screen off freezes the download in its tracks. Resumes again when you switch the screen back on.

Phone/Wifi sleep issue while not plugged in
Hi, I can confirm that this is happening to me with XiiaLive in an identical way.
- 3G streaming works ok
- Wifi + screen on works ok
- Wifi + screen off BUT plugged into AC works ok
- Wifi + screen off => drops the connection after a couple of minutes
I went mad yesterday trying to make xiia work, but then realized that this could be the case and found this post and another one on Modaco (http://android.modaco.com/content/h...s-possibly-a-request-for-the-next-modaco-rom/)
So you actually saved me the time of testing it in other roms, but anyway, which rom have you got ? I have ieftm one.
I can save you the time to test it with other streaming services, I've tried them all hehe.
It could be a phone sleep issue, rather that a wifi sleep.

Well, like I said above, my guess is that the newer version of sense is throttling the wi-fi to save battery life when the phone is idle. The wi-fi is still working but it's capped at a lower speed.
You can test this by installing tunewiki and trying out a few radio streams. 96kbps works perfectly, 128kbps is ok but stutters a little at times. Then when you go up to 192kbps (which I think is the quality last.fm streams at) it can't keep up anymore and the tracks skip.
re:roms - I was on ieftm, am currently on modaco and was on modaco r5 and r6 before that. All of them have the same issue and all are based on the FroYo/Sense roms.

Hm, it´s working just fine for me. Listening to it right now with display turned off, no problem here.
Using the original Froyo on a debranded Desire...

What do you mean by original FroYo? As in vanilla?
From what I can tell it's only happening on Sense roms.

My statement was a little misleading. I was referring to the normal OTA update...

Sibbi said:
My statement was a little misleading. I was referring to the normal OTA update...
Click to expand...
Click to collapse
Hmm. And it's on wi-fi and it's not plugged in to the mains?
Weird. I can't replicate this on any FroYo + Sense rom. I haven't tried an unrooted 2.2 rom, though.
Be good if we could get somebody else on an OTA 2.2 rom to confirm this.

tuatha said:
Hmm. And it's on wi-fi and it's not plugged in to the mains?
Weird. I can't replicate this on any FroYo + Sense rom. I haven't tried an unrooted 2.2 rom, though.
Be good if we could get somebody else on an OTA 2.2 rom to confirm this.
Click to expand...
Click to collapse
Nope, neither on 3G, nor plugged in... Used last.fm quite a lot in the past days and never experienced your troubles. It only runs on Wifi and mostly unplugged.

Very odd. Thanks anyway.
Maybe this is unique to rooted roms, then.
edit: all the roms I've used have had the wi-fi n patch, now that I think about it. Will see if I can find one that's unmodified.

That's a nice finding (about throttling speed). About n patch: it had problems from day one (and I don't need it), but I can't recall if the version of ieftm I installed has it. Any way to check it, or do you know if it was included from the start ?

Fixed. Did a full wipe and installed a rom that didn't have the wireless n patch. Problem gone.
Sibbi, thanks for posting. Wouldn't have occurred to me otherwise.
Anybody else experiencing an issue with streaming radio/podcasts over wi-fi while the screen is idle, you can grab a rom without the wireless n patch here:
http://android.modaco.com/content/h...-froyo-pre-rooted-no-hboot-with-radio-deodex/
Pick one of the 'with radio' roms. Odexed or deodexed doesn't matter. Make sure to do a full wipe first.

Nice ! Any way to remove the n patch without changing rom ?

Don't know. It could be as simple as extracting the rom and removing the patch, but I couldn't say.
If we could find out where exactly the N patch is and what it's called, I'd be willing to try it out.
You'd still have to wipe and reinstall though

I'll try to find the original n patch and see what changes in regards to modaco original rom

forum.xda-developers.com/showthread.php?t=707873&highlight=Wireless+patch
This was for 2.1, but it might just be the same hack ? It's a small hex edit and a file substitution (kernel module if I'm not mistaken). Will try it tomorrow if nobody does it in the meantime, too drunk right now ...

I'd be a bit wary of that tbh. I don't know enough to go messing around with it. Especially not at two in the morning, when I should already be in bed.
I did find this part interesting:
"Also in theory WiFi n will most prob drain more battery than WiFi g but in my zip's there is k newer firmware which is suppose to help in battery drain."
I wonder if the improvement to battery drain that he's talking about involved throttling down the wi-fi connection when the phone was idle?! Hmm.

Probably, will mess with it tomorrow after a sleep and a nandroid

[Q] No DInc2 Earpiece Audio - Speakerphone works fine

I finally decided to root/s-off/ROM last week, and after following the many excellent guides around I got to a place where I liked the features and speed of the ROM I settled on (Incredible 2 HD 4.something).
Here's a breakdown of what I passed through to downgrade/s-off/root/recovery/ROM:
Friday
Downgraded from 2.3.4/Hboot0.98. Successful.
Installed CWR, su, busybox. All well.
Boot once into stock VZW GB 2.3.3.
Grab full nandroid backup of "stock" 2.3.3 as a failsafe.
Back to CWR 5.0.2.0. Installed CM7 / gapps. All still well. I wanted Sense back, so hunted for a good candidate ROM.
Settled on Incredible 2 HD from themikmik.com
Initial flash acted like I wasn't rooted (CWR .zip install said (bad) when I selected the ZIP. md5sum is perfect, so it's not a bad copy. Battery pull later and a few full wipes, install is fine.
Saturday
Inc2HD ROM is really sluggish so I decide to nuke it from orbit and start over again.
I grab the Super Wipe script and run.
Reinstall DInc2HD ROM.
Rom is very responsive, acting much better.
Start reinstalling all my apps again.
Deal with the stupid problem of sms messages from VZW (http://www.droid-life.com/2011/06/2...age-from-vzwnmn-here-is-how-to-stop-them/]fix detailed here[/URL]).
Receive and place several calls as normal throughout the day.
Gradually reinstall apps only as I need them. Keeps down the clutter
Sunday
Receive and place several calls as normal throughout the day.
Gradually reinstall more apps only as I need them.
Getting to a good state with apps re-authed and reinstalled. Decide to grab another nandroid checkpoint backup.
Backup is fine, resume normal daily use.
Monday (today)
[*]Alarm goes off as intended (yay - I have 'Clock' back after being missing on my phone since 2.3.3!)
[*]Listen to some spotify paired to my car on the drive into work
[*]Colleague calls me .. and I can't hear him. I figure it's a bad connection so I call him back. Still can't hear him through the earpiece. As a quick test I switch to speakerphone, I can now hear him.
I figured this was a one-time thing, but start test calls to DInc2 from my desk.
Damn - earpiece isn't passing any audio. Speakerphone toggle gets me audio, as does plugging in my 3.5mm earphones.
I then test other apps I know I can toggle to playback through earpiece, and no dice (Google Voice, etc). All I can hear is a very very faint buzz while a call or playback should be coming from the earpiece. When I hang up, the faint buzz in the earpiece goes dead again.
Made sure bluetooth radio was off to rule out pairing to other devices (though I haven't re-paired since wiping anyway). No wifi radio on either. All alone with the mobile network radio.
Now I know I've done a lot to the phone over the weekend, but I can't find any common cause of what might have happened between the last good call I placed on Sunday evening and today (Monday). Phone sat all night charging on my nightstand. No physical damage or anything like that.
Thinking this may be a ROM or app issue, I bounce back to my known-good snapshot of the 2.3.3 stock ROM. Problem persists - crap.
To further rule out, I full wipe and install CM7.1.0.1 from scratch just to get another baseline. Still no earpiece audio - getting frustrated!
Whatever it is, it isn't exhibiting signs of being a ROM or app issue because it persists full wipes (wipe/cache clear/dalvik wipe, and another pass even with the super-wipe script).
Yes, I've checked basics like making sure In-Call Volume is not muted. I've also installed Audio Manager to make sure there's not some lurking audio volume problem. All sliders maxed before, during and after test calls.
Uninstalled any audio-related app to attempt to remove any hold on audio output. But recall here - it's following across ROMs and wipes, so this is just busy work.
Logic says then that either
I hit some rare bug?
The process of mucking around with recoveries, ROMs, and other lower-level items has flipped a bit somewhere that will persist full user-space wipes/partitions/formats.
it's faulty hardware (which I have a hard time believing, but stranger things have happened!) This would just have to be horrible timing.
Searches on here and other sites don't bring up too much for the Incredible 2 and this kind of earpiece issue. There's a passing mention of a "silent audio bug" here, but doesn't seem relevant (nor much detail given).
I've grabbed output 'c:\> adb logcat -v time -b radio > alogcat.radio.txt' while making a call and switching between earpiece (default) and speakerphone. No really good clues there. Changes in logging verbosity didn't show too much of interest. I'll pastebin it after I scrub my phone number out if anyone's interested.
So after the wall of text ... anyone have any ideas?
I'm in it to win it with this, so I'm not unrooting and warrantying this pig I'm due for a new phone but there's nothing I want other than to just have my DInc2 back working.
I'm off to keep searching. Wondering if there are other debug-level tools/switches via adb that'd let me poke at devices, but I'm guessing those interfaces may not be as readily exposed as I'd like.
Thanks in advance all.
tl;dr - Incredible 2 earpiece randomly stopped working, but speakerphone and headphones still output phone call audio fine. Follows across wipes/ROM installs. LOLWTFBBQ?

I hate to say it, but your earpiece is probably broken... U may have smashed it with your keys in your pocket (did that on og dinc)...
Sent from my Incredible 2 using xda premium

If speakerphone and headphones work, but you cannot get sound at all from the earpiece then that would lead to me to be hardware issue... Electronics break man.. unfortunately.. and when you try to think that there is nooo way possible that you could've broken it, that's usually when you do.
Sent from my Incredible 2 using xda premium

faehsemc said:
If speakerphone and headphones work, but you cannot get sound at all from the earpiece then that would lead to me to be hardware issue... Electronics break man.. unfortunately.. and when you try to think that there is nooo way possible that you could've broken it, that's usually when you do.
Click to expand...
Click to collapse
Fair enough. I hadn't ruled out full-on hardware failure I just found it to be the least-likely of the candidates.
I had to replace the speaker in my original Incredible, so I figure it can't be too much tougher to do in this one. I'm going to exhaust some other troubleshooting first (my wife has a functional stock DInc2 that I want to compare some logcat output from, see if anything stands out when making a standard voice call).
I'm always careful to change ONE thing at a time then test to make sure my variables are where I expect them to be, so this one threw me. I'll post back with results, and hopefully get my earpiece back .

OK, I ordered a replacement earpiece and replaced it. This did not fix the audio. I tested both the original earpiece and the new earpiece before installation by using a low speaker-level source and confirmed that BOTH actually work fine and produce sound as expected.
While the phone was disassembled, I made sure all contact points were good for the earpiece. This isn't a physical problem.
So, this takes me back into the software/firmware/radio arena.
And more specifically, in order to persist all wipes and reinstalls, this has to be something below.
I'm going to use adb to flash a radio (I think there's one newer than the one I have installed, something.622? Not down at bootloader to check right now).
If this doesn't do it, anyone want to buy a DInc2 for parts and dev?

The newest radio is .1111 before that .722
Sent from my Incredible 2 using xda premium

Good call on the 1.09.01.1111 firmware. I found and flashed that instead of .722.
No effect unfortunately.
So next I'm thinking that perhaps whatever kernel I brought with me from the first ROM flash could have jacked something up in terms of audio modules or packages. It's a long shot, but I'm going to grab something like nc2_2.6.35.14#21-2.3.4.zip (non-AOSP) and flash that.
Now that I have ruled out actual hardware failure, I'm just too stubborn to give up on this .. open to productive ideas on things to check, methods to troubleshoot or rule out, etc. TIA.

What about Tue hardware connection from the speaker to phone itself? I don't know much of the board on the phone so I can't give you ideas of where to test, but if you can see where the leads go I would say follow it
Sent from my Incredible 2 using xda premium

Right. I disassembled the phone again late last night and traced back to the extent I could follow. I didn't find anything glaringly obvious or bad.
Also of note, if I'm in a super-quiet room and keep the earpiece near me with no call in progress, I hear literally nothing. As soon as a call is initiated, I hear a very faint "sputtering" sound from the earpiece (original or new earpiece), which means the symptom here clearly impacts either speaker.
So something upstream from it ... whatever pathway sends audio to this device isn't getting instantiated properly? That'd make me look to the kernel or driver to understand what pathway does work when routing audio output to the rear speaker that doesn't properly route it to the earpiece for the same call.
Recapping for my own sanity:
- Physical causes == none seen, mostly ruled out via disassembly and inspection, earpiece replacement with known-good part and known-good reassembly.
- Radio == upgrade to .722, .1111 and back to .622, no change.
- ROM == not likely culprit (problem persists any ROM replacement)
Can't fight off the nagging feeling that the act of starting down the road to S-Off + su + rooting did something here.
Given that there are guides to un-rooting (don't think you can un-S-off per se though, right) I may give that a shot since this phone is essentially a guinea pig now. Going to see how far down this rabbit hole I can go.
While I'm stewing on that does anyone have links to android filesystem reference material? I'm thinking the high-level relation between things like bootloader, recovery partition, user-space filesystem and on which levels I can address these with tools like adb. I want to try to understand if some bit could have been flipped at a layer lower than what flashing a ROM or kernel can recover, but perhaps higher than a baseband radio flash. Knowing where all these live and how they interrelate sounds interesting to me. Then I can form a better working theory on what could cause the stupid problem I'm having and if it's plausible to be in software/firmware somewhere.

There is an unrooting guide on YouTube. I find it hard to believe its software, but I work on a radar weapon system that has proven me wrong many times... But if you have flashed multiple roms then the kernel would've been reflashed atleast once and if you are doing a full boot and system wipe, whatever drivers previously installed would have been overwritten... I'm leading to believe there is a shorted componant on your board and because the voltage is so low on these, there moght not be any visual evidence. Unless u have schematics of what voltage is applied where, there isn't a way to test most of them. Especially if the gates are set to be low when applied, vice highs. I would s-on factory reset and of that doesn't work, its hardware
Sent from my Incredible 2 using xda premium

Agreed. I work with enterprise hardware/storage/cluster systems, so I'm driven by nature to root cause this silly thing - but yeah, occam's razor seems to say here that it's just a really stupid coincidence that some random component failed just at the time I began making other changes. And I can't let it go
This is even more frustrating to me because I always make a point to introduce only one change at a time then test the outcome!
After poking through the SDK/reference guide about AudioManager, I was reminded that GV has access to the earpiece audio path. While I could just make test calls in/out, this saves me from burning minutes in the process.
As a quick-and-dirty workaround (for anyone who may stumble on this in the future), you can use Google Voice to act as an internal earpiece playback test tool.
Install and then go to settings and tell it to play back via the earpiece by default and not the speaker. Then (assuming you have voicemails to play), attempt playback. You can toggle between the two audio outs in a much quicker way than I've seen in any other app. Works close enough for me to serve as a test tool as I make discrete changes as I go through troubleshooting.
Maybe there are other media playback apps that'd offer a toggle to the earpiece for playback (but why?), though I didn't look. Seems like the AudioManager reference guide implied that the earpiece was a more "protected" audio path than the speaker (but that's likely just for actual carrier network voice calls).
Cheers,

I'm really getting a kick troubleshooting.. I've been recruiting for a year and a half now.. miss working on gear.. one and a half years left and back to my ship... Can't wait
Sent from my Incredible 2 using xda premium

I actually doubt it's your ROMs --- I'm running latest unmodified vz gingerbread and all of a sudden about 5 days ago I could no longer get earpiece to function - my only guess is something shorted out because of an off-market USB charger that I got 3 of for 7 dollars off Amazon...
Anyways, I had the same sorta flutter that you seem to hear when on a call and there should be sound... and otherwise silence when silence is expected... anyways I replaced it with a brand new earpiece and EXACT same issue is happening still.
Not sure whats up but this may be the world telling me to use my Bluetooth headset more anyways... I'll post if I find anything that fixes it, but I ain't gonna hold my breath given how few ppl seem to be experiencing this issue.
Good luck

Phone crashes in car dock on AOSP ROMs

Here's the deal. I have an iBolt car dock (that specific really shouldn't matter) and Tasker profiles to turn on GPS, Bluetooth, etc while my phone is plugged in. Been like that for months. Up until about a week and half to two weeks ago, my phone app would crash when trying to receive a call while in said dock. The message I got was "unfortunately, the process com.android.phone has stopped". When I noticed, I was running Carbon. I clean flashed the nightly I was on and same result. I then tried Deviant, Slim, JellyBeer, PAC-man, etc. All of them gave the same result. Same wipe procedure for all of them. Same apps as I've always had. I then flashed AOKP M1 and everything worked. Then I tried Task's AOKP. Same thing. Everything worked. I don't get it. I posted the issue without a logcat (as pulling one of those while driving is a no no) in those respective dev's threads but it seems they don't know what's going on with everyone else. Hence, this thread. If you are running any of the ROMs I mention and experienced the same problem, post here. If you have logcats (ballsy), even better. I figure this would be the best way for all the devs of those ROMs to see what is happening and so the problem can be nailed down.

I'm also using an iBolt dock. Posted this in Xone Deviant thread: http://forum.xda-developers.com/showthread.php?t=2215840&page=55
itsmikeramsay said:
Not 100% sure bro, haven't been able to test it...
Click to expand...
Click to collapse
CrackerTeg said:
@ itsmikeramsay. Did you see this a few pages back? Thoughts?
Click to expand...
Click to collapse
Same here. Phone ui crashes when call is initiated but call goes through. Catlog attached.

Glad to see someone else feels my frustration with this. I battle this issue all the time. I have 2 iBolt docks(the regular one & the pro dock) & have had this issue with both. If not the not the incoming calls freezing the phone, its the phone rebooting when pluging it in, or the dev will update the rom and the usb audio doesn't work at all. I'll give task's AOKP a try to see how things with it. I was a huge fan his roms in the past up untill an update and the usb audio stopped working. In that situation, I usual just try a couple different roms untill one works. But then, the incoming issue happens or it reboots when docked and I feel like throwing my phone out the window
btw, i got an email today about the prodock cables being shipped. I've been using the one that came with the first iBolt
If my wallet would allow it, I would buy a headunit with bluetooth and use a NFC chip to put the phone in dock mode and not have this issue regardless of what rom i'm running. but my wallet stays empty
---------- Post added at 01:16 PM ---------- Previous post was at 12:41 PM ----------
I'm pretty sure the usb audio out working on some roms/updates vs. not working others is due to something in the kernel. Ex. I flashed the latest deviant xone update(2.0) and the didn't work. So I reflashed the previous version (1.0 stableish) and the audio works.
I hope this gets resolved 'cause I enjoy listening to podcasts & playing ingress during my commute only to have it ruined by a phone call that freezes my phone, rebooting booting and listening to my wife "quit ignoring my phone calls"
Sent from my SGH-I747 using xda premium

Interesting. My complaint has nothing to do with the audio out portion of it as I use my phone for browsing and as a phone. I have my tablet or iPod for the music in my car. So the complaint has nothing really to do with the iBolt but the phone being docked and not being able to use the actual phone function. If the usb audio gets fixed, bonus but I'm much more concerned with the primary function of this device.

After doing a bit of research, it seems that samsung didn't implement call audio through the dock connector. I know this is not your direct complaint BUT if you are using the ibolt cable that has the dock resistor( that tells the phone to go in dock mode) and the Rom/kernel is trying to route the audio via the usb than the phone may be getting confused. I think the solution to your issue, since your not concerned about audio out, is to replace the supplied cable with a standard data/charging cable. I haven't tested this theory, but i'm pretty sure taking the dock resistor out of the equation will fix the phone freezing when receiving a call.
I did have a rom installed at one point that had audio out working AND didn't freeze on incoming BUT had an unrelated bug that drove me nuts, so flashed another rom. It's too bad I can recall which rom and which release it was

Thing is, I have a Parrot bluetooth adapter that my calls go through. They don't go through the dock at all. I have a tasker profile that triggers the phone to go into car mode with Google's no longer supported Car dock app when the device is plugged in. It also turns on bluetooth, GPS, blah blah. Like I said in the OP, everything was just peachy up until two weeks ago where something in those ROMs got borked. Either way, I'm now running Carbon's latest and the issue is gone. Whatever got messed up is now fixed. I wish I knew what it was tbh but I can't read git.

I would like to add my two cents.
I too have an iBolt dock for SGS3, and an after-market radio with bluetooth.
I have tried several ROMs (CM stable, LiquidSmooth, ParanoidAndroid), and all of them exhibit the same behavior:
Going into the docked mode is flakey at best. 90% of the time the phone doesn't recognize it has been docked.
Now comes the "best" part: on disconnect from the dock the phone's bluetooth stack apparently crashes. The bluetooth connection gets immediately lost, and the phone's bluetooth status is stuck in 'ON' position. After that there is no way to turn the phone's bluetooth 'OFF' and back 'ON'. The only way to restore is to reboot the phone.
I haven't tried to pull the logs from the phone yet, but it may be possible if I take the dock home and try to repro the condition.
Not asking for answers, just voicing my frustration hoping to draw dev's attention to the problem.

ROM comparison CM11 vs S3Rx

Yet another ROM comparison. I've been using CM since I got this phone in May 2013. I love CM. It is clean, fast has a ton of nice features and is NOT TouchWiz. I've been loyal to it since I got this phone. I had it on my previous Atrig 4G, too. The problem is that not everything works in CM on the d2att. I blame Samsung for this, but do not really know where the blame lays. I read reports that Samsung withheld the source which made it tough to get everything working correctly. The Bugs list on CM for this phone is not complete mainly with regards to Dock and Bluetooth, IMO. I have not tried any other AOSP ROMs, but some of these bugs may be there as well.
I recently decided to try the latest 4.4.2 stock rom and it seemed to work OK, but I had to freeze and uninstall so much stuff. I discovered S3Rx and am now very happy with my phone. I still have TouchWiz showing its ugly head (most prevalently in the pull down and dialer/incallUI), but now everything works!!!! The new modem NJ1 has better sensitivity (I can get calls in places when I had no signal previously). Bluetooth works correctly. I can have multiple BT streams and not lock up the phone (Audio and serial or serial and phone). Previously, it would drag down and both would eventually fail. BT connects more reliably and readily. I have not tried dock audio, but there is a selection for it and I am guessing it works. (I did try dock USB audio and not only does it work, but it is not noisy like it was in CM10/early CM11 when it was functional) The only niggle is car dock identification. When you place it in the dock, the car mode icon illuminates, but no app is launched. I had to create a Tasker profile to get it to launch the old Android Car Home app. To get the home button to resume to the Car Home app (known issue with car home), you need to enable the car home button through an exposed framework module. It all seems to just work. Also, no random reboots.
Hope this helps someone who is still trying to get life out of this great piece of hardware. If you are struggling to get the phone to do all it should do and are frustrated with CM, I recommend this rom

keithspg said:
Yet another ROM comparison. I've been using CM since I got this phone in May 2013. I love CM. It is clean, fast has a ton of nice features and is NOT TouchWiz. I've been loyal to it since I got this phone. I had it on my previous Atrig 4G, too. The problem is that not everything works in CM on the d2att. I blame Samsung for this, but do not really know where the blame lays. I read reports that Samsung withheld the source which made it tough to get everything working correctly. The Bugs list on CM for this phone is not complete mainly with regards to Dock and Bluetooth, IMO. I have not tried any other AOSP ROMs, but some of these bugs may be there as well.
I recently decided to try the latest 4.4.2 stock rom and it seemed to work OK, but I had to freeze and uninstall so much stuff. I discovered S3Rx and am now very happy with my phone. I still have TouchWiz showing its ugly head (most prevalently in the pull down and dialer/incallUI), but now everything works!!!! The new modem NJ1 has better sensitivity (I can get calls in places when I had no signal previously). Bluetooth works correctly. I can have multiple BT streams and not lock up the phone (Audio and serial or serial and phone). Previously, it would drag down and both would eventually fail. BT connects more reliably and readily. I have not tried dock audio, but there is a selection for it and I am guessing it works. (I did try dock USB audio and not only does it work, but it is not noisy like it was in CM10/early CM11 when it was functional) The only niggle is car dock identification. When you place it in the dock, the car mode icon illuminates, but no app is launched. I had to create a Tasker profile to get it to launch the old Android Car Home app. To get the home button to resume to the Car Home app (known issue with car home), you need to enable the car home button through an exposed framework module. It all seems to just work. Also, no random reboots.
Hope this helps someone who is still trying to get life out of this great piece of hardware. If you are struggling to get the phone to do all it should do and are frustrated with CM, I recommend this rom
Click to expand...
Click to collapse
Be careful with this type of post as it encourages competition between devs.
Just an option, but how about just "reviewing" Roms,
I created a thread on " whats your favorite Rom and why" and a day later it was pulled by the moderator.
CM has come along very well recently

Build 13.0-20160207 "Unfortunately, Bluetooth Share has stopped."

Is this a known issue with the D851 and CM13? I keep getting a force close over and over and it won't stop unless I reboot the phone witch in turn disables Bluetooth. I can't seem to find anything about it other than one post with no answers. Here is a pic of the build causing the problem. Any way to fix this?

Same issue here. Seems to be caused by a commit to lg g3 update init in the cm changelog.

Interesting. I decided to drop down to 13.0-20160206 and Bluetooth works, however "Unfortunately, Bluetooth Share has stopped." message has only shown up once so far. Bluetooth sound in "Star Trek Timelines" is slowed down, like the bit rate is low or something. Have not tried anything else yet.

SovereignKnight said:
Interesting. I decided to drop down to 13.0-20160206 and Bluetooth works, however "Unfortunately, Bluetooth Share has stopped." message has only shown up once so far. Bluetooth sound in "Star Trek Timelines" is slowed down, like the bit rate is low or something. Have not tried anything else yet.
Click to expand...
Click to collapse
Looking at the changelog for the next potential nightly, it seems like it will be fixed. They added back part of that file.
See http://review.cyanogenmod.org/#/c/132118/

Anyone flash 20160212? I not only have the bluetooth issues, but mobile data regularly drops out, requiring an Airplane Mode cycle to regain.

UPDATE: re-flashed, GPS is working fine.
I dirty flashed 20160212 and now my GPS doesn't work, but the Bluetooth messages have stopped on my D851.
mdphoenix said:
Anyone flash 20160212? I not only have the bluetooth issues, but mobile data regularly drops out, requiring an Airplane Mode cycle to regain.
Click to expand...
Click to collapse

CM maintainers Forget our Device is BCMD unlike their devices.. so they think if it works for them, it must work for all.......
Only the D851/D856/F400/LS990 use BCMD while the others use that wcn crap.
as for data. Leave that to CM to mess that up to............. I had to go and fix my Device tree for PAC that CM totally screwed up.
your data issue is more a apn-cong.xml issue.. if you want a fix to that.. go read the last few pages on my Pac thread. and I listed a fix for data issues..............

Nice. Thanks!

..

Had this issues on an earlier build fixed it by reflashing

MuF123 said:
What was the fix?
Click to expand...
Click to collapse
A long hard road followed all of this. Lessons were learned, and in the end, nothing really gained. Except a working phone.
The entire issue started when I tried to flash SuperSU. Not knowing that CM didn't use SU. That began the decline. I ended up using the LG flash tool to put it back to an older stock version. It worked for a while, then I rebooted and it went to hell. Deader than dead. I shipped it off to a guy in Texas I found on Ebay to JTAG it. Came back just fine. Except I think whatever I did to it before then jacked up the charging. The phone wouldn't charge at all. Sitting on a charger for two days gave it about 5%. Come to find out, it was still under warranty. I shipped it to LG. They fixed it, returned it, and now it's on stock Lollipop, and I have to say - I quite like LG's interface. I've turned off a few things, installed Nova, etc. But at this point I have no reason to root or go custom. I did with my VZ phones because they were such nazis about everything. But I've got free tethering with Tmo. The phone works well. So, I'm sticking with what I have for now.