Fascinate Bluetooth stereo bug in Samsung code fixed in cyanogenmod

Fascinate Bluetooth stereo bug in Samsung code fixed in cyanogenmod - Fascinate Q&A, Help & Troubleshooting

I've been happily running the GEEWIZ 2.6 ROM alternately with GEEWIZ kernel and KGB kernel. No problems at all except for the Stereo Bluetooth connection to my car.
The phone works great on newer versions of my car 2009 Acura TSX and other phones work fine on my car.
Well I (via Google) finally narrowed the problem down. There is a bug in the native android 2.2 and 2.3 code that Samsung pushes right through. HTC for example fixed the code in their phones.
Google this: "Issue 9888oor A2DP sound quality". I added the word Acura as well.
Cyanogenmod 7.2 RC1 does not have this bug and the phone sounds fine on my car. Would it be possible to extract or port the A2DP code from Cyanogenmod 7 and place it into GEEWIZ or other more stock ROM's?
The reason I want to stay more stock is that I can't get SMS delivery confirmation to work in Cyanogenmod 7 or 9 or Gummy 1.0 and SMS confirmation works well in GEEWIZ 2.6.
I have tried GO and HandCent SMS clients in addition to stock and have checked all combination's of receive and sent notifications and delivery requests and reports. None work. Texts get through fine just no confirmation. Verizon to Verizon should work.
I don't have enough posts to post in the Dev/GEEWIZ thread. Can someone help or cross post please? I've read until I'm blue in the face on both of these issues. ;-)
BTW, I have 2 fascinates and both act exactly the same.
Thanks!

Zong00 said:
I've been happily running the GEEWIZ 2.6 ROM alternately with GEEWIZ kernel and KGB kernel. No problems at all except for the Stereo Bluetooth connection to my car.
The phone works great on newer versions of my car 2009 Acura TSX and other phones work fine on my car.
Well I (via Google) finally narrowed the problem down. There is a bug in the native android 2.2 and 2.3 code that Samsung pushes right through. HTC for example fixed the code in their phones.
Google this: "Issue 9888oor A2DP sound quality". I added the word Acura as well.
Cyanogenmod 7.2 RC1 does not have this bug and the phone sounds fine on my car. Would it be possible to extract or port the A2DP code from Cyanogenmod 7 and place it into GEEWIZ or other more stock ROM's?
The reason I want to stay more stock is that I can't get SMS delivery confirmation to work in Cyanogenmod 7 or 9 or Gummy 1.0 and SMS confirmation works well in GEEWIZ 2.6.
I have tried GO and HandCent SMS clients in addition to stock and have checked all combination's of receive and sent notifications and delivery requests and reports. None work. Texts get through fine just no confirmation. Verizon to Verizon should work.
I don't have enough posts to post in the Dev/GEEWIZ thread. Can someone help or cross post please? I've read until I'm blue in the face on both of these issues. ;-)
BTW, I have 2 fascinates and both act exactly the same.
Thanks!
Click to expand...
Click to collapse
No problem, I'll have a look at it for you and see if I can fix that in GeeWiz for the final release. Thanks for PMing me, by the way, I was about to post GW 2.8, but I would like to be able to include this too!

thanks
I would be happy to test any change. I'm getting used to flashing every night now. ;-)

Well, I ported over what I *thought* was everything they did in CM 7.2 and all that I managed to do was destroy the ability to pair with a device so far
I dug out my old BT audio receiver and I can certainly hear that it sounds like garbage by default. Well, it wasn't THAT bad but I do see, er hear, what you are talking about.
My concern is that my receiver is old and crappy (it is), and I may never be able to actually hear any difference. That said, I will keep trying for a while, if I can at least pair with the receiver after changing something I will pass it along to you and see if it does something useful for ya!

From what I understand the Fascinate with stock software works on older Bluetooth devices OK. I don't know that for sure because I don't have an older bluetooth device. On my car, the stock Fascinate does not have any fidelity, it produces sound via bluetooth like an AM radio with clicking sounds. When updated to Cyanogenmod 7.2, the sound is very FM like with no clicking sounds.
I appreciate the effort!
thanks,

OK, I finally got back to this. I was replacing too many modules, I toned it down a bit to just replace the bluez audio module and the a2dp module. I can absolutely hear a difference now!
It's still Bluetooth, aka not perfect, but I can crank the volume on the Fascinate up much louder before it "splats" (that's a very technical audio term) and overall it just sounds much much better.
I've attached a test version of an update-zip you can try. Should work with Clockwork Mod and/or my GeeWiz Recovery, but I've only tested with the latter of course . I will be making a more official version for GeeWiz 2.8 (I may go ahead and release a 2.8.1 with this, it's a pretty big fix -- who cares if I said there would be no more updates, right? LOL)
THANK YOU for pointing this out to me!! Let me know what you think!

Not yet
No joy -
First I tried loading the patch over fullwipe GEEWIZ 2.8 and KGB 12/31.
Next I tried loading the GEEWIZ kernel over the KGB kernel.
And finally I tried loading the full 2.8.1 system file.
The sound is still not nearly as clear as Cyanogen 7.2 RC1.
I'm sure if the new build is somewhere in the middle or not. Seems like the full fidelity is present now but the clicking sound is still present.
Cyanogen BT is as clear as a direct audio connection. At least to my old ears.
I'll revert back to 2.8 and try the audio test again.
Do you think a full wipe would help - can't imagine why.

Zong00 said:
No joy -
First I tried loading the patch over fullwipe GEEWIZ 2.8 and KGB 12/31.
Next I tried loading the GEEWIZ kernel over the KGB kernel.
And finally I tried loading the full 2.8.1 system file.
The sound is still not nearly as clear as Cyanogen 7.2 RC1.
I'm sure if the new build is somewhere in the middle or not. Seems like the full fidelity is present now but the clicking sound is still present.
Cyanogen BT is as clear as a direct audio connection. At least to my old ears.
I'll revert back to 2.8 and try the audio test again.
Do you think a full wipe would help - can't imagine why.
Click to expand...
Click to collapse
Full wipe probably wouldn't do anything for ya, no. When you say clicking, is it fairly often, or more like once per song? I get what sounds more like a skip (to me) about once per song, I didn't think it was the same complaint, but perhaps it is? If so, at least I can duplicate it, so that's good.
I'm not sure if much more can be done, the only remaining difference is the audio.conf (trivial changes) and the libbluetooth C library itself, and replacing the latter causes the Fascinate to not be able to pair. I think source would be required to properly replace that module (CyanogenMod has that particular luxury). It could be in the Java code, though. If that's the case it can still be fixed.
I'll poke around some more and see if I can do anything else for ya. I was jamming all night over bluetooth last night, honestly I didn't even know the device could do that a few days ago - LOL.

djp952 said:
Full wipe probably wouldn't do anything for ya, no. When you say clicking, is it fairly often, or more like once per song? I get what sounds more like a skip (to me) about once per song, I didn't think it was the same complaint, but perhaps it is? If so, at least I can duplicate it, so that's good.
I'm not sure if much more can be done, the only remaining difference is the audio.conf (trivial changes) and the libbluetooth C library itself, and replacing the latter causes the Fascinate to not be able to pair. I think source would be required to properly replace that module (CyanogenMod has that particular luxury). It could be in the Java code, though. If that's the case it can still be fixed.
I'll poke around some more and see if I can do anything else for ya. I was jamming all night over Bluetooth last night, honestly I didn't even know the device could do that a few days ago - LOL.
Click to expand...
Click to collapse
The clicking sound in my car occurs several times a second and its really obvious. Acura blamed the phone (Samsung) saying just that the phone wasn't compatible but I wasn't convinced until I found the Android bug ID.
I really appreciate the effort and it sounds like you fixed a problem just not my problem. ;-)
I'm considering a Galaxy III this summer but Samsung has left a bad taste in my mouth.
Let me know if you come up with anything else to try.
thanks!

Well, I spent some more time on this, and found that Samsung actually does include the BT code with their public distribution. So ... I spent some time merging that with the Cyanogenmod code that's currently available on github, and gave it a try. Short version: fail. Sounds like crap again and still skips intermittently for me. I can't replicate your more frequent skip, I'm afraid, but this was certainly a step backwards regardless.
Next I tried replacing all the modules my custom build generated with the ones from CyanogenMod 7.2 RC1. Even bigger fail, no bluetooth at all.
Using custom build with the BLUEZ modules from CyanogenMod restored the sound quality but it still skipped. Basically back where I started, so fail. I don't see the code edits they made that improve the fidelity so much, maybe they haven't committed them yet?
Last try was to set Master=true in the system/etc/bluetooth/audio.conf file on top of everything else. Still skips, but maybe a little less often? Still chalking it up as a fail.
So I think I'm not going to be able to fix this for you. There's a chance that what they did in CM 7.2 RC1 is just not posted yet and I can still make a custom set of binaries that will work, but I'm not very optimistic about it. I think what I did in GW 2.8.1 is pretty much as good as I can get it. Sorry
I did the best I could. For what it's worth, BT audio on my Fascinate is light years better than it is on my Galaxy Nexus at the moment. Not much consolation for you, but it's something I guess. The fact that I was able to generate a set of working BT binaries from source is also a good thing, even if they didn't solve anything since that means if I even stumble upon the fix it's something I can build myself!
You're welcome to try my final attempt, I've attached the .zip to this post. This is a custom BT module build with the BLUEZ modules with the ones from CM 7.2 RC1 and the master=true setting in audio.conf. I really don't think it will solve anything for you, but the only way to be sure is to try, right?

Related

Kaosinate BUG list

I decided to make a thread for kaos that gives a more complete set of incomplete/broken things so he doesn't half to. I will try to keep this up to date as possible and if you see something that has been fixed that i have listed as broken please post and I will correct it. I will try to do as many detailed things as possible for now and as things are fixed I will remove them and if a fix is required to be applied manually will try to include it also. Keep in mind this is an unofficial thread and I am not responsible for anything you do to your phone. Now to the list (PS if this is an inappropriate posting area feel free to move it)
Data: FIXED entirely update to latest build
Wifi: FIXED update to latest build.
Bluetooth: Somewhat working, will pair but won't connect.
Browser: UPDATE: fixed, still crashes on flash and javascript some though according to people in irc.
USB notification: no usb mount notification not sure if USB mass storage will work or not but adb still works so a work around is using the commands adb push and adb pull (google on how to use these commands if you dont know already)
Vibrate notifications: vibrate works on the stock messaging app fine but I can't get it working on go sms. Workaround would be just use the stock notifications.
Quadrant: quadrant doesnt work for me gets stuck at database writes, not a big deal no known fix though
Sensors: FIXED update to latest build
Headphone jack: Headphone jack is now fixed somewhat. Still buggy to a degree some headphones won't work (it seems to only work for headphones that have a mic built in for me but it could be just hit and miss with all headphones).
Haptic feedback: haptic feedback in general doesn't work. No known fix
Camera: Currently not working. No known fix.
Cyanogen Settings has some things that make the phone freeze, DO NOT ENABLE JIT its not working yet.
Recovery: Currently broken for me and some other people. Not sure if its working for others (kaos's works and has been apparently.) JT said it shouldn't be a hard fix for him in the future (likely next release?) Use odin to get back to stock and restore your backup from before you had CM installed if you made one if you want. (report any problems in thread please) UPDATE: Greyone and Kaos informed me that recovery works if you go to recovery mode and select advanced > reboot recovery (thanks!)
Wireless tethering:Works if you use the Wireless tether app! fix found by ae55. Might work with other wireless tether applications but it WILL NOT work with the wireless tether in the settings menu.
USB tethering: Not working for me (try it and post if it works for you, its in settings, wireless and networks) more than likely a 3rd party app like easy tether would fix this as long as your 3g is working
MMS: MMS also does not currently work. A workaround is to simply get the message sent to your email for receiving but it seems that the sending of gmail messages isnt working atm i just did a test message to my number and it is sitting in my outbox. Been there for a good bit so its more than likely not sending it. A 3rd party application could fix this possibly? Update: Message finally went through it took a solid 15-20min though so I wouldn't rely on it myself. Again, 3rd party app would prob be your best bet around this. IT DOES NOTIFY YOU IF YOU RECEIVE AN MMS JUST WONT DOWNLOAD IT!
ADW launcher app drawer: not really a bug just many users have looked for this and cant find it, its pretty simple to fix just longpress on the homescreen and tap custom shortcuts then the adw launcher things then app drawer. Hope this clears some things up.
YOUTUBE: seems as though the youtube application isnt playing videos, I dont have good enough service to test it but I will take everyone in the threads word for it. Other video playback apps seem to be having trouble too.
Pandora: Currently my pandora isnt working, could just be me but i think its a problem with the 3g still.
Thats all that I can find for now that isn't working but its likely I missed something, I more than stress to keep in mind Kaosinate is still a VERY alpha build. Its about a 50-50 split between things working and things not working for now but it is coming along thanks to Kaos' work on it and I invite everyone to follow him on twitter and join IRC for the MOST up to date information about this ROM.

Edit: Nevermind. Haven't checked his tweets (well, his reply tweets). Good write up.

bendbowden said:
From Kaos' thread:
Click to expand...
Click to collapse
Kaos permitted and favored this thread on his twitter. (check it)

wirless tether worked for me on v1

Sound hound doesn't work lol. Can't recognize any song that it could before.. Not a hardware issue but still
SCH-I500 Kaosinate FROYO/Cyanogemod 6

Cannot delete files using root explorer
rm: no such tool

so far i love this rom. here are the few things i have noticed so far, some are probably known already
-unable to setup an exchange 2010 account. I fixed it by loading a new e-mail.apk i found in CM forums.
-Unable to watch videos. sling, vevo, movie trailers.
-Some funky thing happened when i powered the phone off. had to pull battery.
minor things i know, but i wanted to point them out.

I get no service from verizon at all. Roaming symbol then no service. Dunno why. Will try flashing again later when I have easy access to odin
Sent from my sch-i500 using dj05 w/ stupidfast kernel

my slingplayer works.. i get a "There was a problem while playing" error for youtube.

daavy said:
my slingplayer works.. i get a "There was a problem while playing" error for youtube.
Click to expand...
Click to collapse
Same here, YouTube does not work. No big deal.
I just want my GPS

aes55 said:
wirless tether worked for me on v1
Click to expand...
Click to collapse
]\
I would love to know how this is possible when the wifi drivers wont even load... post up some pics or something.
EDIT: Kaos has informed us that the drivers do load its the wifi scanner files that arent working yet.

BartJJ said:
]\
I would love to know how this is possible when the wifi drivers wont even load... post up some pics or something.
Click to expand...
Click to collapse
here you go
EDIT: This is with the stand alone "wireless tether" app

aes55 said:
here you go
Click to expand...
Click to collapse
Interesting I'll update the thread to include such information

2296 in quadrant...
To fix the rm: no such tool prompt;
Threax said:
Thanks this works perfectly. You can even do it in root explorer by navigating to /system/bin/rm and choosing rename from the long press menu and renaming it rm.old. Don't forget to mount rw at the top.
Click to expand...
Click to collapse

Sling started working after reboot but I found a few others.
Pandora and Sirius wont stream
Speakerphone no workie
Sent from my SCH-I500 using XDA App

The latest Swype beta works wonderfully in Kaosinate v2.
There is an extra step you have to perform to get it working.
Download and install the swype installer from your beta.swype.com page. Install swype. It will force close when trying to configure swype after the install or generate a license.
Delete the libSwype.co from system/lib/. Then reinstall swype and voila! You will have a fully working, fully up to date, swype keyboard.
--I'll post this in the kaosinate thread too to make sure everyone knows it works. I was dying w/o it.
Edit: just realized someone already posted this in the kaosinate thread so i'll just leave it at this post.

Anyone else still getting the skipping in audio with this? Damn annoying..
SCH-I500 Kaosinate FROYO/Cyanogemod 6

Audio only skips when you change the volume or something of that sort for me, not a real big deal.

Does it a ton during playback for me
SCH-I500 Kaosinate FROYO/Cyanogemod 6

Neuman.Tim said:
Anyone else still getting the skipping in audio with this? Damn annoying..
SCH-I500 Kaosinate FROYO/Cyanogemod 6
Click to expand...
Click to collapse
My notification sounds do this if the screen is off. Play briefly then stop, soon as I wake the phone it continues to play

[Q] CM 7.1 low sound volume and a market that keeps freezing

Hello, for the past few weeks i've been using cm 7.1 on my i9100 and I'd be glad to say that the rom is perfect, if some issues didn't come up. Firstly, since the first day of use, i've realized that the sound volume (both from speaker and headset) is fairly low compared to samsung's rom (to be frank going above 50-60% in volume options doesn't make a difference). Is there any solution to this? CM 9 apart from the "known issues" got that bug too?
The second problem came up a few days ago and it's related to the android market app. Everytime you scroll through an app's details, the phone freezes and the only way to restore it, is to turn it off and on again. Currently, i'm using app brain which doesn't seem to have that problem, but i really love google's app. So, any solution to that?

Try the app in my sig to give the headset/headphone volume a boost, works really well & only distorts the volume at very high levels (>75% which you shouldn't need). There are apps on the Market which can boost the speaker volume, not sure how well these work as I haven't tried any.
So far as the Market is concerned, I use a CM based rom and have had that problem as well. The only fix I've come across/read about is to restore a much earlier version of the market (hopefully someone else reads this thread and has a fix that can help both of us ). I haven't done this myself as I've trained myself to do all my scrolling thru app details on my PC first & simply do the install/update on my phone without scrolling thru the details , but I'm sure a search on here should dig up something/the apk you need.

Ask in the right place may get an answer quicker .
http://forum.xda-developers.com/showthread.php?t=1176411
jje

[Q] Camera does not work or open - Cyanogenmod 10

First off here is my info:
Phone: AT&T Samsung Galaxy Note i717
ROM: Cyanogenmod 10 quincyatt nightly build 12/23 (in attempt to remedy my problem)
Using this guide http://forum.xda-developers.com/showthread.php?t=1958944&highlight=install+cyanogenmod in installed the 11//14 stable build initially without too much trouble.
I did find right away that I was unable to locate any camera application or any way to access it other than the lockscreen shortcut.
When I attempted to use the shortcut from the lockscreen it simply does nothing. It doesn't crash my phone, but it also does not open my camera.
I also tried installing a couple of camera applications from the play store and they start up, but the camera never activates.
This problem persisted even when I upgraded to todays nightly build 12/23, also so far I have noticed no new problems with this build as opposed to the 11/14 stable build.
I have searched for a solution for this problem in the forums, and perhaps I missed something, if that is the case then please direct me to the proper thread.
I tried posting this in the development section only to find out that I am unable to (I've been using this site for a while but never needed to register to ask a question).
If anyone has had this problem and/or knows how to fix it I would greatly appreciate your input.
I apologize if I have left anything out, if I have then let me know and I will get back to you as soon as I can.
Edit: I updated to the 12/24 nightly build today and it appears to have resolved the camera issue right away. If anyone else is having this problem then I hope this helps.

ill give $5 to the person that fixes this.
tatzelworm said:
First off here is my info:
Phone: AT&T Samsung Galaxy Note i717
ROM: Cyanogenmod 10 quincyatt nightly build 12/23 (in attempt to remedy my problem)
Using this guide http://forum.xda-developers.com/showthread.php?t=1958944&highlight=install+cyanogenmod in installed the 11//14 stable build initially without too much trouble.
I did find right away that I was unable to locate any camera application or any way to access it other than the lockscreen shortcut.
When I attempted to use the shortcut from the lockscreen it simply does nothing. It doesn't crash my phone, but it also does not open my camera.
I also tried installing a couple of camera applications from the play store and they start up, but the camera never activates.
This problem persisted even when I upgraded to todays nightly build 12/23, also so far I have noticed no new problems with this build as opposed to the 11/14 stable build.
I have searched for a solution for this problem in the forums, and perhaps I missed something, if that is the case then please direct me to the proper thread.
I tried posting this in the development section only to find out that I am unable to (I've been using this site for a while but never needed to register to ask a question).
If anyone has had this problem and/or knows how to fix it I would greatly appreciate your input.
I apologize if I have left anything out, if I have then let me know and I will get back to you as soon as I can.
Edit: I updated to the 12/24 nightly build today and it appears to have resolved the camera issue right away. If anyone else is having this problem then I hope this helps.
Click to expand...
Click to collapse
I have the same problem.

Fixed?
James Musacchio said:
I have the same problem.
Click to expand...
Click to collapse
Well as I stated in my edit, the 12/24 nightly appears to have fixed this issue so far as i can tell. Also updated to the 12/25 nightly and the camera still works. One bad thing about this is that I have experienced more than a few reboots, but my phone starts up so fast afterwards that its a small price to pay for having my camera back.
As always, make a backup before you flash the newest nightly but I haven't seen too many problems other than the occasional crash of a couple apps and the unfortunate reoccurring crash of Apollo which is annoying.
Let me know if this fixes your issue, if it does then I'm glad I could help.

Tried CM10 nightly myself tonight, and was quite happy with it, until ....
Random reboots ....5 in 3 hours.
Camera is good, but the menu button was iffy ....
It's getting better, but I'm gonna stay with my backup for a bit longer I think ....g

12/25 is a bit sketchy
gregsarg said:
Tried CM10 nightly myself tonight, and was quite happy with it, until ....
Random reboots ....5 in 3 hours.
Camera is good, but the menu button was iffy ....
It's getting better, but I'm gonna stay with my backup for a bit longer I think ....g
Click to expand...
Click to collapse
Yeah I decided to try the 12/25 build and didn't notice any improvements from the 12/24. Ironically about an hour after my last post my phone then went into a reboot loop that I couldn't stop until I removed my battery. I had to boot into cwm recovery and then reflash the 12/24 build. So far this is the most stable nightly that allows for the camera to work without causing too many issues besides one incident I had the first day I flashed it.
I recommend people stay away from 12/25 as it was extremely unstable in my experience. I may try the 12/26 build simply because I can, but I'll definitely keep the 12/24 on hand if that fails as well.

[Q] Nexus LouderBoom (AwesomeBEATS)

First of all, I'd like to say I'm glad to be on this extremely helpful forum with very intelligent members. I have been watching this forum for at least 2 years now to get up to speed on rooting and not being a noob so much. I have successfully rooted, troubleshooted, restored to stock, rerooted and added custom roms on my GSM/HSPA+ Galaxy Nexus from Google Play due to help on these forums and elsewhere and I am very grateful. Because I am new, I was not able to post this question in the forum I wish to, which I have mentioned below, until I reach 10 posts, so please do bare with me.
I have been on Android 4.1.2 due to a sound tweak rom by the name of Nexus LouderBoom.zip which installs the AwesomeBEATS sound equalizer enhancement to the ridiculously low volume of the Galaxy Nexus. I never updated to 4.2.2 for fear that it wouldn't work and also because the upgrades for that particular OS version weren't that necessary to me.
However, I did happen to stumble upon ...Awesome...'s thread on AwesomeBEATS™ v.5 and perused it's pages to see that many people are having success with it as it has now been to designed to work with pretty much any Android Jelly Bean operating system. So I decided to give it a go and update to 4.2.2 via OTA. Prior to the OTA update, I made sure I did a back up through Nexus Toolkit 1.6.3 as well as make a Nandroid backup via TWRP Custom Recovery.
The update went well and everything worked normally. I then applied the AwesomeBEATS v.5 rom via the recovery console and installed it. It had the option under the Sound Settings like it's supposed to. I then began customizing my sound preferences for Headset, Speaker and Bluetooth for which I momentarily noticed a sound change when manually adjusting the equalization in the "Speaker" while playing a song via Google Music. However, after switching to Bluetooth, the adjustments no longer registered and it seemed to bypass the fact that the tweak was installed on the phone. Even after turning off Bluetooth and going back to Speaker, it just didn't work anymore. I even tried to flash an older version (v.4) to no avail as it made the streaming from Google Music quit entirely. Because of this incompatibility, I had to revert back to my previous version 4.1.2 where I was able to utilize the Nexus LouderBoom.zip tweak which worked beautifully.
Looking back on why v.5 didn't work for me, I can only stop at this line in the instructions...
"*STOCK Rom (ROOTED but on stock rom. (ONLY SOUND FILES WILL INSTALL)"
Is the fact that the ONLY the sound files will install part of my problem? Or is there some other technicality I missed along the way?
Thank you so much for anyone who responds... or not.

[ROM][S5 Sprint/Boost/Sport]Un-Adulterated CM12 5.0.2

As always, you are responsible for your device. Use common sense and make backups
In case anybody wants a pure cm12 for the kltespr, here it is. Was built from cm12 sources, 5.0.2.
Downloads below
Use lollipop gapps, Link Below
I installed over an NKD leak build, after doing a full wipe of data, internal sdcard, cache, system...all of the things
I had a problem with TWRP 2.8.3, so I used the one I built a while ago, link below
***Flashing Directions***
Boot to recovery
Wipe everything
Flash rom zip and gapps zip
***Updating directions***
Boot to recovery
Flash newer version of this rom
Wipe Caches
Everything seems to work so far.
I plan on making some changes, but figured I would throw up a "vanilla" cm12 thread in case anybody wanted it and didn't want to build it themselves.
***Recoveries***
My old TWRP 2.8.0.1-gt build
https://www.androidfilehost.com/?fid=95864024717072487
md5sum 93f46caaac3ce006af5d60795ad16ec8
***GAPPS***
Lollipop GAPPS
http://downloadandroidrom.com/file/gapps/5.0/gapps-lp-20141109-signed.zip
***Downloads***
Original Manual Build
Fully tested and all seems good
https://www.androidfilehost.com/?fid=95864024717072482
md5sum b99c37e1df51739dec9181147ab86c8b
First build with an automated build script
Please let me know if anybody tests this, because I have not yet, but the only changes are pulls from upstream CyanogenMod
https://www.androidfilehost.com/?fid=95864024717073976
md5sum c9c252b907547e44b480046fd82273da
New Build 1/5/2015
Pulling in upstream changes, new su and terminal app included
https://www.androidfilehost.com/?fid=95887005526786941
md5sum 76d264f0fabe38bcef8eb3ecdea84c6b
New Build 1/7/2015
Fixed updater script, more upstream changes. No need to re-flash GAPPS anymore when updating to the newest version, just flash then wipe caches.
https://www.androidfilehost.com/?fid=95887005526788129
md5sum 1366c215ddfa8e46d117c6760f7af441
New Build 1/8/2015
UNTESTED - Pulled in lots of changes from CM upstream, please let me know how things go.
https://www.androidfilehost.com/?fid=95887005526788863
md5 9b2c549705edc80533dc78fc19d3d206
New Build 1/12/2015
Pulled in more upstream commits - see review.cyanogenmod.org branch:cm-12.0 status:merged between Jan 8th and Jan 12th
https://www.androidfilehost.com/?fid=95897840722641504
md5sum b3ace7b8581cbbd55616a70d46ef4e2b
New Build 1/20/2015
Pulled in more upstream, including theme stuff, testing now
https://www.androidfilehost.com/?fid=95897840722646871
md5sum 88c44248bde68284c3878c4c2cf31952
Another New One for today 1/20/2015
Pulled in more upstream, attempt fix on battery drain, inverted colors, themes, notification panel options in settings and a few more things I think
https://www.androidfilehost.com/?fid=95897840722646992
md5sum f4f8ee1e6c9f65ac4852e96ab1c3e629
1/24/15 Build
Honestly didn't really dig through CM changelog, but it seems like the noise is gone, and I don't really know why but it feels generally snappier and less laggy in certain spots
https://www.androidfilehost.com/?fid=95916177934516437
md5sum 44cc73da8b931f0f17aedd5695d8c32a
1/26/15 Build
Lots of Bluetooth updates, along with a few other upstream changes
https://www.androidfilehost.com/?fid=95916177934517707
md5sum 2e4d62f5c00105572ea8ad34d38b3d97
1/26/15 Boost Mobile Test build
I have no idea if this will fix the Radio problem, and no way of testing, so please let me know...Everything is the same as the Sprint build with one or 2 tweaks to try to force it to Boost
https://www.androidfilehost.com/?fid=95916177934517723
md5sum d252b3f5ed04749b8c4fae496ef7b600
Build 1/27/15
Pulling in a few changes I missed yesterday
https://www.androidfilehost.com/?fid=95916177934518355
md5sum daa24071a13ea36330e1c9455b3a7bf0
Build 1/27/15 Boost Mobile
Pulling in a few changes I missed yesterday, Boost Mobile build
https://www.androidfilehost.com/?fid=95916177934518385
md5sum 60062ccc93e7cce2ccd5f40bc5c83b21
Build 1/29/15
Nothing super special, just pulling upstream changes. Missed a few regarding new wallpapers, will be in the next one
Sprint Version
md5sum f3afc625e033c4a7483437ff560e0ec3
Boost Mobile Version
md5sum 4b1f0d2d85d21aeac2561b8f572a1fdd
Build 2/2/15
Pulling upstream changes, looks like some audio and video fixes are included. Still need to pull a few things into my forked repos, but most important commits should be included.
Sprint Version
md5sum 0bc3710bc2fc89dec965b1d18ed95d9e
Boost Mobile Version
md5sum 2143fde6f85f8f5f35a4ca685f79712f
Build 2/6/15
Pulling upstream changes, been a few days and I honestly haven't checked the commit list other than those of my forked repos. Not much special in my forked repos but I am sure there has been plenty of changes upstream in the other repos
NOTE - I haven't tested this build yet, got a few things to do before I can flash it
Sprint Version
md5sum ddb910a56806078529e7359e61412737
Boost Mobile Version
md5sum 0b323c7e8a401fcc9f4c3af65789c915
Initial S5 Sport test buildSorry not working yet
md5sum 5e10ff86a819a4abf48e697490572685
2/9/14 Build
Sprint Version
md5sum 817cc516c6a7547be34b88efa10ceecf
Boost Mobile Version
md5sum d2250ff799ca3ae0ca89995ae1ea0ffc
New Sport test build
Sport Test Build
md5sum 67259518bcc973292eb59f802ae50fbd
Test build 3 for sport, manually modified kernel image with fstab info that was missing and a few other things
Sport test build 3
md5sum 1dc912e626afa448b4b52309d3c4d594
Test build 4
Sport test build 4
md5sum 54403b46c3370cac21df3bece0b24b56
2/14/15 Builds: Should include the 4k camera, snapshots from video and a few other things from upstream. Changes pulled in on the 13th, so anything commited on or before the 13th will be included. Friday the 13th Builds
Sprint S5
md5sum 730365184f1fce03aec31a45ef3a3e9a
Boost S5
md5sum 9b51e4e3ffd1090228cd1a440a78d16b
S5 Sport Test Build #5
md5sum 30baeac0f03c396f0bbb247a4b727ccf
2/18/15 Builds: Does not include wifi scan fix to raise the time between wifif scans, and may have missed a commit or 2 from upstream.
Sprint S5
md5sum 5779e6ca7a5c67f9314dc1059a66cfbd
Boost S5
md5sum 257cb01c561dc63013d5d264fd319673
2/24/15 Builds: Does not include wifi scan fix to raise the time between wifi scans, sorry I fogot to put them in. Fixed the BT problem from last build and pulled in all upstream changes.
Sprint S5
md5sum 1fee6e21e0d16ce0fa116b7a297128b4
Boost S5
md5sum 12a27e7286606af9b188d8fc554f0457
New Sport test builds, these are untested please make a backup before flashing:
test 6
test 7
3/2/15 Builds: Pulled upstream, attempted to change wifi scan interval. Did not test yet, let me know how it goes and if the wifi scan helped
Sprint S5
md5sum f7a2582ef3645892bafd857620da72e1
Boost S5
md5sum c66fc6844b67052d4e495c32588b0586
3/9/15 Builds: Pulled upstream, rebuilt sport sources from the ground up and initial tests are good. Changed build status to weekly and bumped version number.
Sprint S5
md5sum 70281b5359094529af1d2c046923c11b
Boost S5
md5sum 52669293004ba88d84e7422df8cacd02
S5 Sport
md5sum ad13c803d0783ddd82abd0717816492f
3/16/15 Builds: Pulled upstream, trying some new libs on sport build
Sprint S5
md5sum a6bf3da9c8a5d121a2dbfa5734504209
Boost S5
md5sum 8debd7379852d975e03fbf7c7001a8b4
S5 Sport
md5sum 7f41290fe813e967124ff49cef0160f5
3/25/15 Builds: Pulled upstream, nothing else to speak of
Sprint S5
md5sum b0f21e568f49ab6595381d41f27664a7
Boost S5
md5sum 86baf09812f18f8d8628e010eda919b4
S5 Sport
md5sum 28c3a16e7d1b37d951641a2d1b0ec152
***Firmware files for non sport models***
These MUST be flashed in odin, and can be flashed right over your CM install to update your baseband
OA6, no system, no kernel, no recovery
***Thanks***
CyanogenMod Team
The Muppets
Team Nocturnal
Any and all testers of my work, especially those who donate(it is always appreciated)
***Big Thanks to all those who have Donated***
@ToeJullar @Remesar @jphoff @Stealth5325 @jared-wallace @robak1965
Someone also donated without logging in, I can see your real name in paypal but not sure if you want me to mention it. Please let me know your username if you want a mention, and thanks again!!
If you feel that I forgot you please let me know
***Sources***
https://github.com/Linuxdork/android
If you would like me to link you recoveries, gapps or anything else here just let me know and I will be happy to put it in.

Bluetooth, wifi, NFC, Phone, and camera all seem to work fine. No FCs at all yet. Installed a bunch of apps all working fine, even facebook.
Wifi hotspot works, didn't test any other forms of tethering
Must flash gapps to get to the setup process. Tap n go works for account setup. Tap n pay works on the vending machines near me, one time it took 2 taps to pay but that was probably my fault.

Got the incoming call bug fixed, will reserve this post for other known bugs
All in all this feels pretty stable considering how early it is in the Lollipop game, I am using it as my daily driver and haven't been let down by it yet.
**Bugs**
Reported from users:
Moving apps to SD seems to be qwuirky, reports of SD formatted as Ext-SD through philz working, but other formats not working
Time problems - Manually set time zone, instead of leaving it on automatic and things should work fine
Help me find more!!

miked63017 said:
Got the incoming call bug fixed, will reserve this post for other known bugs
**Bugs**
Help me find some!!
Click to expand...
Click to collapse
Thank you very much for the straight CM12 build. This helped me, because it confirms that many (not all) of the problems I've been having with other CM12 builds on kltespr appear to be in the base, and not tweaks or mods. Here's a list that I just posted over in @vinman12 Team Nocturnal CM12 thread.
The good:
Camera, video, audio (with a wired connection), WiFi & mobile data are all good.
The bad:
Bluetooth connections are iffy, at best. BT sharing crashes & BT audio device connections are hit or miss.
Phone calls have been randomly troublesome. Most of the time the dialer works great calling and receiving. There are other times I have to retry 2 or 3 times just to get dialing started. Sometimes I can answer a call, but neither of us can hear the other one even though the connection still appears live. And sometimes the dialer won't disconnect after a call is finished, and even killing the app doesn't free the connection requiring a reboot.
Let me know if you want logs sent. If so, how: PM, just posted here, stuck on pastebin or whatever else you prefer.
Greg Robinson

greogory said:
Thank you very much for the straight CM12 build. This helped me, because it confirms that many (not all) of the problems I've been having with other CM12 builds on kltespr appear to be in the base, and not tweaks or mods. Here's a list that I just posted over in @vinman12 Team Nocturnal CM12 thread.
The good:
Camera, video, audio (with a wired connection), WiFi & mobile data are all good.
The bad:
Bluetooth connections are iffy, at best. BT sharing crashes & BT audio device connections are hit or miss.
Phone calls have been randomly troublesome. Most of the time the dialer works great calling and receiving. There are other times I have to retry 2 or 3 times just to get dialing started. Sometimes I can answer a call, but neither of us can hear the other one even though the connection still appears live. And sometimes the dialer won't disconnect after a call is finished, and even killing the app doesn't free the connection requiring a reboot.
Let me know if you want logs sent. If so, how: PM, just posted here, stuck on pastebin or whatever else you prefer.
Greg Robinson
Click to expand...
Click to collapse
I have heard about everything mentioned, I have yet to run into any of the bluetooth stuff personally but I have noticed the phone call problems. I did actually cherry pick a few commits from a few different repos to get the RIL working properly, so I guess in one way the cm12 base has been slightly modified. I did want to keep it as clean as possible to track the state of base as well, but I do plan on cherry picking more commits here and there to test things. Before pulling in the RIL changes you couldn't even answer the phone, it just used some weird built in ringer that went off until you rebooted, even after the call hung up.
I will try to stay up to date with what other people are doing to fix these problems, but really this build was more for getting a good Lollipop build env setup for other things. I do plan on getting nightlies going, in case you couldn't tell by the filename , but I can't say for sure how much this is gonna stray from base. So I guess for now, if the bugs are in base, and other builds, they will most likely be here too.
Can you give me a good way to run into the bluetooth problems you have had? I only use it for phone calls in my vehicle and haven't noticed any probs yet, it also seemed to work fine for the tap'n'go account setup when I first installed the rom.

miked63017 said:
I have heard about everything mentioned, I have yet to run into any of the bluetooth stuff personally but I have noticed the phone call problems. I did actually cherry pick a few commits from a few different repos to get the RIL working properly, so I guess in one way the cm12 base has been slightly modified. I did want to keep it as clean as possible to track the state of base as well, but I do plan on cherry picking more commits here and there to test things. Before pulling in the RIL changes you couldn't even answer the phone, it just used some weird built in ringer that went off until you rebooted, even after the call hung up.
I will try to stay up to date with what other people are doing to fix these problems, but really this build was more for getting a good Lollipop build env setup for other things. I do plan on getting nightlies going, in case you couldn't tell by the filename , but I can't say for sure how much this is gonna stray from base. So I guess for now, if the bugs are in base, and other builds, they will most likely be here too.
Click to expand...
Click to collapse
And, of course, everything is working perfectly now that I'm actively trying to make something fail while I'm running logcat.
Hey, I know: it's Heisenburg's fault! We can only see when something fails or collect debug data, but not both at the same time. Because uncertainty. Those deranged quantum bastards hosed everything up for all of us normal geeks.
---------- Post added at 09:26 AM ---------- Previous post was at 09:19 AM ----------
And to prove my theory, about 2 seconds after I Ctrl-C'd logcat and cleared it to try again, BT failed in the middle of my favorite AC/DC song. But on the bright side, I have a 9MB logcat file of exactly zero bugs.

greogory said:
And, of course, everything is working perfectly now that I'm actively trying to make something fail while I'm running logcat.
Hey, I know: it's Heisenburg's fault! We can only see when something fails or collect debug data, but not both at the same time. Because uncertainty. Those deranged quantum bastards hosed everything up for all of us normal geeks.
---------- Post added at 09:26 AM ---------- Previous post was at 09:19 AM ----------
And to prove my theory, about 2 seconds after I Ctrl-C'd logcat and cleared it to try again, BT failed in the middle of my favorite AC/DC song. But on the bright side, I have a 9MB logcat file of exactly zero bugs.
Click to expand...
Click to collapse
Lol, well if you get a logcat with the error send it over and I will take a look. I will look around and see if there is any BT specific commits we can pull in to try.
Sent from my SM-G900P using XDA Free mobile app

I left CM12 because it had issues playing videos in Chrome, but I think I'll give this a shot later Thanks for sharing mike!

ghostzyden said:
I left CM12 because it had issues playing videos in Chrome, but I think I'll give this a shot later Thanks for sharing mike!
Click to expand...
Click to collapse
My pleasure, fwiw my daughter has been watching crap all day on my phone in chrome, mostly YouTube(apparently chrome is default app when hitting a link). I do know that I cannot play videos in chrome from my plex server, but the plex app worked when I briefly tested it, and plex worked with chromecast.
Sent from my SM-G900P using XDA Free mobile app

miked63017 said:
My pleasure, fwiw my daughter has been watching crap all day on my phone in chrome, mostly YouTube(apparently chrome is default app when hitting a link). I do know that I cannot play videos in chrome from my plex server, but the plex app worked when I briefly tested it, and plex worked with chromecast.
Sent from my SM-G900P using XDA Free mobile app
Click to expand...
Click to collapse
Ok appreciate it

Anybody notice any other bugs? I see the download counter going up but not much feedback. I haven't rebooted at all since I flashed it, 2-3 days, wondering if everyone else's experience is the same? Anybody else using the hotspot, do you have a tile for it in the notification panel? It looks like its supposed to be there but I didn't see it originally so I found a sqlite table to add to and got it working, but not sure if it works out of the box for anyone.
Sent from my SM-G900P using XDA Free mobile app

miked63017 said:
Anybody notice any other bugs? I see the download counter going up but not much feedback.
Click to expand...
Click to collapse
Not a problem here, just not much time or functioning brain cells to test & post results today.
I started over with a serious cleaning and repartitioned with the original Samsung PIT and a full erase in Odin. Then I installed the NKD firmware from @tdunham, immediately followed by your CM12. Since then, everything I had trouble with on CM12 has been totally stable. No BT issues, no phone issues, and not horrible battery life.
I'm going to give @vinman12's latest Team Nocturnal CM12 another test later this evening or tomorrow morning. I plan to use the latest TW Lollipop for a few solid days after that.
I'm wondering if those of us who frequently flash back & forth among firmware versions, boot loaders, TW & CM have "polluted" our partitions enough over time that simple formatting leaves too much crap in the sd cells that rarely get zeroed out. My I/O is definitely faster after the fresh PIT install.

greogory said:
Not a problem here, just not much time or functioning brain cells to test & post results today.
I started over with a serious cleaning and repartitioned with the original Samsung PIT and a full erase in Odin. Then I installed the NKD firmware from @tdunham, immediately followed by your CM12. Since then, everything I had trouble with on CM12 has been totally stable. No BT issues, no phone issues, and not horrible battery life.
I'm going to give @vinman12's latest Team Nocturnal CM12 another test later this evening or tomorrow morning. I plan to use the latest TW Lollipop for a few solid days after that.
I'm wondering if those of us who frequently flash back & forth among firmware versions, boot loaders, TW & CM have "polluted" our partitions enough over time that simple formatting leaves too much crap in the sd cells that rarely get zeroed out. My I/O is definitely faster after the fresh PIT install.
Click to expand...
Click to collapse
Agreed, I think a wipe should dd /dev/zero to the partition instead of just formating. But theoretically speaking I don't think it should make a difference because any data left over should be written over as new data is saved, and not be skipped to make fragmentation. But I do notice "oddities" when jumping back and forth a lot.
Either way, glad the problems went away, and fwiw I flashed a clean NKD leak in Odin prior to flashing this as well.
Sent from my SM-G900P using XDA Free mobile app

Updated OP with latest build, untested, but it pulls in some upstream code changes from the CM team. Also, re-formatted OP.

Rom
As of right now im having no problems. Installed earlier today and gonna let it run a few days before i say anything. I have noticed that i cant play NBA jam game, the touch screen doesnt work when the game loads. Could be on their end or it just could be a CM issue. Anyway, thanks for the stable rom!

[ROM] Un-Adulterated CM12 5.0.2
miked63017 said:
Got the incoming call bug fixed, will reserve this post for other known bugs
All in all this feels pretty stable considering how early it is in the Lollipop game, I am using it as my daily driver and haven't been let down by it yet.
**Bugs**
Reported from users:
Same, or similar BT bugs as other CM12 builds. I haven't ran into them but I only use BT for calling from my vehicle.
Same, or similar phone call flakiness bugs as other CM12 builds.
Help me find more!!
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This has happened twice. I'm using the bot build as of 1/2/15. This also happened with another 5.0.2 CM based rom I tried. The only way to get out of that message is to take the battery out and restart. Any ideas what causing it?

Prince_Basil said:
This has happened twice. I'm using the bot build as of 1/2/15. This also happened with another 5.0.2 CM based rom I tried. The only way to get out of that message is to take the battery out and restart. Any ideas what causing it?
Click to expand...
Click to collapse
I have had it happen once while the phone was in my pocket not being used. I had it happen about 5-6 times on the stock NKD leak, I suspect the auto root kernel on that. Not sure why it happens on CM.
Did you get the log from when it happened by any chance? Its definitely a kernel panic, figuring out what is happening right before the panic would help to troubleshoot. If we can figure out why it might be a simple edit in the kernel build.
Whatever other info you can give might be helpful, like I said its only happened once to me while the phone was in my pocket. It just happened to me the day before yesterday, before that I hadn't had to reboot for any reason.
Sent from my SM-G900P using XDA Free mobile app

miked63017 said:
I have had it happen once while the phone was in my pocket not being used. I had it happen about 5-6 times on the stock NKD leak, I suspect the auto root kernel on that. Not sure why it happens on CM.
Did you get the log from when it happened by any chance? Its definitely a kernel panic, figuring out what is happening right before the panic would help to troubleshoot. If we can figure out why it might be a simple edit in the kernel build.
Whatever other info you can give might be helpful, like I said its only happened once to me while the phone was in my pocket. It just happened to me the day before yesterday, before that I hadn't had to reboot for any reason.
Sent from my SM-G900P using XDA Free mobile app
Click to expand...
Click to collapse
If you could show me how to do that I can get it for you. I wiped my phone, I installed your ROM, then installed Gapps, then installed Updated SU root. Then I just started using my phone. Installed all my apps and fixed my settings. Also, I've been having issues with moving apps to the SD card. It says I have no room but its a 32 GB SD card with 22 GBs free. And battery life is really bad. I looked to see what might be causing it and it the highest one Miscellaneous... So I'm not sure what that is. The screen shot only shows 11% because my phone just restarted. But before that it was at 67%.

Prince_Basil said:
If you could show me how to do that I can get it for you. I wiped my phone, I installed your ROM, then installed Gapps, then installed Updated SU root. Then I just started using my phone. Installed all my apps and fixed my settings. Also, I've been having issues with moving apps to the SD card. It says I have no room but its a 32 GB SD card with 22 GBs free. And battery life is really bad. I looked to see what might be causing it and it the highest one Miscellaneous... So I'm not sure what that is. The screen shot only shows 11% because my phone just restarted. But before that it was at 67%.
Click to expand...
Click to collapse
Not sure what you mean by updating SU root, CM has all its root stuff built into the settings menu. Did you flash something for SU, and if so did it include a kernel?
I do notice slightly reduced battery performance, but if I setup the auto brightness control and a few other things my battery is at about 10% at the end of the day. I am sure battery performance will get better as more people begin to work on CM 12.
Not sure the best way to get the kernel logs off the top of my head, but if you flashed a SU package that included a kernel it could be related to your kernel panics.
I will look into the logs and your SD card issue over the next few days.
Sent from my SM-G900P using XDA Free mobile app

miked63017 said:
Not sure what you mean by updating SU root, CM has all its root stuff built into the settings menu. Did you flash something for SU, and if so did it include a kernel?
I do notice slightly reduced battery performance, but if I setup the auto brightness control and a few other things my battery is at about 10% at the end of the day. I am sure battery performance will get better as more people begin to work on CM 12.
Not sure the best way to get the kernel logs off the top of my head, but if you flashed a SU package that included a kernel it could be related to your kernel panics.
I will look into the logs and your SD card issue over the next few days.
Sent from my SM-G900P using XDA Free mobile app
Click to expand...
Click to collapse
https://www.androidfilehost.com/?fid=95784891001616249

Better Mobile App

welcome