yashsingh1/xdaforums huggingface dataset:
[X 2014 Original Android Development] adm1jtg:
I wonder if its a device model specific error as while there is a small lack of bass on my phone its not nearly as pronounced as others seem to be hearing. That said I have made a few changes that make my phone sound better and I thought I would post them here for others to test, my ears are old so not the best tester.

I am on a USA TMOBILE xt1095

I loaded the cm snapshot build

Edited buildprop and deleted everything in the #media section (not needed on cm builds 9/1 and newer)

Copied the audio_effects.conf, audio_platform_info.xml, audio_policy.conf and mixer_paths.xml to system/etc and also copied the audio_effects.conf to system/vendor/etc

BACKUP ALL FILES!!!! I AM NOT RESPONSIBLE IF THIS MESSES ANYTHING UP!!!!

After that I loaded up viper 4 android via the flashable zip (see link below)

Load the viper driver via the program

Turn the ui settings to expert and reboot

Copy the Dolby_HP_Normalized. file to sdcard/viper4android/kernel (you may need to check convolver for the kernel folder to be created)

on speaker tab I only chose optimize speaker

on headphone

enable convolver and pick the dolby file... should be only one choice

Thats It, I am asking for others to test this exact setup as well and see if they also get good results. Let me know either way so we can get this all working properly. The changes submitted yesterday for sound fix have been included in the files posted.

Downloads:

Viper flashable zip file: http://bit.ly/1VNFnmu

Other Files NON FLASHABLE ZIP (just extract files and manually copy as directed above): http://bit.ly/1VNFqPh
[X 2014 Original Android Development] Tommebaas:
Not everyone wants to make changes.

It's great that you found a solution.

But I just want to flash a rom and use it for about 2 months and update or look for a new one.

It has to work great when you just flashed it.

I know this rom isn't fully stable, but it would be great if the sound works as it supposed to be working.
[X 2014 Original Android Development] adm1jtg:
I agree I was asking for help in seeing if my long ***** solution does improve things as if it does and we all agree it gives OP a better idea of what files to look at so he can make a more permanent change. Right now OP has no specifics at all to diagnose the issues. It started a ways back and it sounds horrible with little bass, thats pretty general I was trying to help narrow down what files might be causing this.
[X 2014 Original Android Development] Tommebaas:
It's good that you're trying to help!

Hopefully the problem will be solved :)
[X 2014 Original Android Development] adm1jtg:
Have you tried the 9-09 build? I would say its improved but still not nearly what stock sounds like, Something still missing
[X 2014 Original Android Development] 0.0:
Does the "Ok, Google" hotword work? If not, I am wondering if it's the blobs or the gapps
[X 2014 Original Android Development] Tommebaas:
Not yet. But van you listen to the music with your headphones and enjoy?

That's the important part.

Sent from my Moto X
[X 2014 Original Android Development] Munns86:
It's working for me after updating to 9/9!
[X 2014 Original Android Development] adm1jtg:
ok google for me ONLY works from voice search i have enabled all the any screen stuff and it doesn't work at all just ignores it and treats the command like text.
[X 2014 Original Android Development] 0.0:
did you try to say the hotword from any screen? like in an app?

I wonder if it will ever get fixed. The 8/19 (or 8/18) build it was working perfectly
[X 2014 Original Android Development] Munns86:
Yep! I just walked into the bathroom while at work :) and was able to call on OK Google while in my nest app.
[X 2014 Original Android Development] 0.0:
Alright, looks like we can narrow it down since it is not working on my end. What gapps are you using? Any other files you flashed as well?
[X 2014 Original Android Development] Munns86:
I flash these minimal gapps :

http://xdaforums.com/android/software/gapps-google-apps-minimal-edition-t2943330

Nothing special outside of that.
[X 2014 Original Android Development] adm1jtg:
For the record I used tknano and as started earlier it did not work for me.

BTW anyone running the latest build did you sound/bass issues resolve themselves completely?
[X 2014 Original Android Development] 0.0:
Do you use a XT1095 device?

sent from my Moto X Pure Edition
[X 2014 Original Android Development] Munns86:
Yep.

---------- Post added at 06:43 PM ---------- Previous post was at 06:43 PM ----------

Yep.
[X 2014 Original Android Development] crpalmer:
FYI, my ability to test changes (or make them) is going to be limited for a little bit. I cracked my screen a few months ago and have been using it like that successfully since then. However, yesterday whatever was making it still work gave up and it now looks like that attached image.

Cyanogen has agreed to replace it for me so I should be back in business before too long.

Luckily, invisiblek has his xt1096 working and is actually a much better device maintainer than me so you should be in good shape until I get a replacement!
[X 2014 Original Android Development] adm1jtg:
Ok just took a bit of time and did a CLEAN install of 9/9 with the gapps mentioned above. Unlike my usual daily driver I did NOT load xposed or custom kernel or v4a. What I have found is as follows:

The sound is as others have stated without bass and might even have a hint of interference in background on all songs

The google search does not contain the options for on any page or to train ok google just a from google app checkbox/slider no other options (cant find a work around for this though s6 had same issues till late may when an update was released, these gapps are from April)

Thus my conclusion is that the gapps used dont seem to affect the sound issues at all and since i cannot get google search to give me the on all screens options at all i cannot test that further.
[X 2014 Original Android Development] Munns86:
As for the hot word detection the same thing happened to me after flashing those gapps but then a few days later it just showed up.
[X 2014 Original Android Development] invisiblek:
This is an outright lie.

Oh, here's the magic patch for 32gb xt1096 users too: http://review.cyanogenmod.org/#/c/109045/
[X 2014 Original Android Development] 0.0:
I cleaned flashed the 9/09 nightly and "Ok, Google" does not work from any screen. I don't understand why some users say it works but others, like myself, can't
[X 2014 Original Android Development] nerotix:
Why does jenkins say the build was succesful but there's no new build on the download site nor on cmxlog.com? =o
[X 2014 Original Android Development] Flamehell:
+1
[X 2014 Original Android Development] alvareo:
I find that Cyandelta gets builds earlier for some reason. Happened yesterday too.
[X 2014 Original Android Development] Flamehell:
[MENTION=3857343]crpalmer[/MENTION] mate,do you know something about that?I check it now and it is still the same.....
[X 2014 Original Android Development] crpalmer:
I think that there are problems with one of the build slaves today. I think it has been fixed but it means you have to wait until tomorrow for a build.
[X 2014 Original Android Development] Flamehell:
Tnx a lot mate!!;)
[X 2014 Original Android Development] murso74:
Anyone else having MMS issues?
[X 2014 Original Android Development] MeanderingCode:
Not connecting to cellular data network

Just flashed the 4/19 nightly over Motorola's stock 5.0.3 build, wiped data, cache, and dalvik, and the device doesn't connect to AT&T's mobile data network on LTE or 3G. Wifi radio works fine.

Am I missing a radio update that Android 5.1 needs?
[X 2014 Original Android Development] twistkill:
You did not do THAT!!!!!!:eek:
[X 2014 Original Android Development] 0.0:
I am sorry to burst your bubble, but you have to completely wipe your device. CM and stock ROM are two very different ROMs
[X 2014 Original Android Development] MeanderingCode:
What does "completely wipe" consist of? I have tried to wipe system, as well, before installing and it still does not connect to mobile data. The zip contains a boot.img and system.dat.new, which look like partition images, but nothing that looks like it's for vendor or contains radios, etc.

EDIT: Messing around with APN settings, i eventually got it to connect to ATT LTE data.
[X 2014 Original Android Development] 0.0:
If you've wiped system, data, cache, etc. then you should be fine. I did not know or saw you mention the system wipe. Well, good thing it was only an APN setting and you fixed the problem

sent from my Moto X Pure Edition
[X 2014 Original Android Development] Flamehell:
[MENTION=2281583]0.0[/MENTION] Sorry mate,before i had a nexus 5,and when i came from 5.0 to 5.1 i had to flash the new bootloader and radio....why you don t have to do that with cyanogenmod?Tnx a lot :)

P.s: [MENTION=3857343]crpalmer[/MENTION] the new nightly is amazing!!!now the wakeup screen is faaaast!!!!!Tnx bro!!!
[X 2014 Original Android Development] 0.0:
You still have to install the radio, but his problem was solved just by messing with APN settings. 5.0 radios and baseband is fine with CM

sent from my Moto X Pure Edition
[X 2014 Original Android Development] zander21510:
So my Moto X will be arriving later today, big fan of CM with all my devices. Glad to see 12.1 going up and all the cool Moto-X specific sensors being used, big props to the developer [MENTION=3857343]crpalmer[/MENTION]!

One question I wasn't able to find searching this and the old 12.0 thread, does slow-motion video work? My fiancee showed it off on her iPhone and I was hoping to use it with my new phone. I favor using Google Camera with the photo sphere and HDR+, but with the nexus I had to flash it as a system app vs downloading it from the store. So has anyone been able to use slow motion? Thanks!
[X 2014 Original Android Development] murso74:
Is not on the cm camera... Maybe flashing the moto one?
[X 2014 Original Android Development] abiezer:
I'm not getting MMS either. Anybody else?
[X 2014 Original Android Development] enochpc:
I have tried this and still don't get a gps lock under cm 12.1. Have reverted to stock as I am traveling the next week. Should I do a fresh install instead of recovering from a back up?

The lock is achieved on 5.0, never installed the leak, I then reboot to recovery and wipe and restore backup of my cm 12.1 install. I verify gps through both maps and GPS test. Nothing but wifi location data on cm 12.1. I'm sure I just did something wrong. I love the rom otherwise, so much faster than stock.

Thanks in advance
[X 2014 Original Android Development] sudhamsu:
[MENTION=3857343]crpalmer[/MENTION], I see the fade-in in ambient display is instant now, but this affects both hand-wave invoke and also notification invoke/breathing. Is it possible to let the display fade-in normally in the case of notifications? The instant fade-in makes sense only for hand-wave or any other user-interaction. It is kinda distracting when the ambient display just pops on with full brightness while breathing.
[X 2014 Original Android Development] murso74:
Also, the phone seems to "breathe" at a pretty high rate when there is a notification
[X 2014 Original Android Development] Tommebaas:
And did it break anything else?

Do I change this with root explorer or something?
[X 2014 Original Android Development] 0.0:
That is why I said to test. But in my testing with phone calls, the other person can hear me so that's a good sign. Idk if it breaks anything else

Yes, you can change this with root explorer. I'll upload the file instead so that it'll be just a copy, paste, and fix permissions
[X 2014 Original Android Development] Tommebaas:
Awesome!

Thank you.
[X 2014 Original Android Development] adm1jtg:
Been testing a little bit now, bass is fixed, phone calls work just fine, netflix streaming sounds fine and nothing I have done on the phone all morning seems negatively affected. GREAT WORK!!!!

Have you done a diff compare on the standard file in the 9/9 build and yours so it can more easily be turned into a commit? If you cant I will have time later today to do it just not this morning?

EDIT: NM found time to do it, the changes are not massive. I made a new file with only the 2 line items that DIDNT involve voice and for me STILL works great. Can a few other please check as my MODIFIED version only contains 2 line changes as opposed to the original 10 changes.

Only added in:

<device name="SND_DEVICE_OUT_SPEAKER_AND_HEADPHONES" acdb_id="9" />

on line 31 and

<device name="SND_DEVICE_OUT_HEADPHONES" acdb_id="9"/>

on line 36

If this works as well as the original should make it VERY easy for one of the devs to add

*** Link Removed*** *We need all the edits not just the 2
[X 2014 Original Android Development] vista178:
Not so patiently waiting for the next nightly for my xt1096. Excited to be able to finally us cm on this device.
[X 2014 Original Android Development] tacosrdelicioso:
The buildbots seem to be be confused. Haven't built anything for a couple days for us and many other devices
[X 2014 Original Android Development] vista178:
Yea, Jenkins shows complaints. I just really want CM12.1 and I don't have the means to roll my own. :P
[X 2014 Original Android Development] mikeoswego:
I was experimenting with call recording earlier and have posted the build I made for that. It includes all the commits at least up to and including the "init: add xt1092" commit. It does not have the /system/etc/audio_platform_info.xml edits included so you'll need to do that if you want to test the audio changes mentioned earlier. It does include the commits that are supposed to help the 32gb device problem.

Here it is: cm-12.1-20150910-UNOFFICIAL-victara.zip
[X 2014 Original Android Development] vista178:
I'm downloading now. Thanks!
[X 2014 Original Android Development] 0.0:
Anyone in the U.S., are you able to get Android Pay to work when adding a card?
[X 2014 Original Android Development] mikeoswego:
I had a Discover card in Wallet. After installing Android Pay, I tried to set it up, it went through a BanCorp agreement and then said Android Pay cannot be used. I'll be happy to collect logs if you want them. I tried to set up a MasterCard and got the same sequence of events.
[X 2014 Original Android Development] 0.0:
Supposedly root is the problem. Unless CM finds a workaround, we will have no Android Pay
[X 2014 Original Android Development] mikeoswego:
I tried disabling root and then rebooting but that didn't change anything. I'll try this on the stock rom later tonight for a data point.
[X 2014 Original Android Development] tacosrdelicioso:
Trying the network fix via a teamsek build. Works like a charm!
[X 2014 Original Android Development] mikeoswego:
On the stock rom with SuperSU, Android Pay came up with the same error. I tried removing root and still got the same error. I tried a complete fresh install of the Verizon rom and then Android Pay refused to run because "Google Play services need to be updated" (even after updating it.) I gave up at that point.
[X 2014 Original Android Development] 0.0:
Thanks for trying. I read on reddit that you need to disable root if on SuperSU and disable SuperSU itself, which you did. I am surprised that didn't work. CM is another issue. It reminds me of when Google Wallet first came out and similar problems came about. Maybe it's a server issue
[X 2014 Original Android Development] Tommebaas:
Is the audio fix included in the next nightly or do I have to do it manually?

Sent from my Moto X
[X 2014 Original Android Development] 0.0:
It should be fixed in the next nightly
[X 2014 Original Android Development] Tommebaas:
It's probably the amplifier commit right?

Sent from my Moto X
[X 2014 Original Android Development] felipevsw:
Tell me more about this network fix
[X 2014 Original Android Development] :
I just started upgrading nightlies at the end of the week instead of everyday. This week CM has been good to me and no known random reboots or quirks so far. I guess that's the best way to go about it.
[X 2014 Original Android Development] adm1jtg:
Todays build 9/11 is definitely one to load, it has the audio fix for low/no bass sound

---------- Post added at 08:36 PM ---------- Previous post was at 08:35 PM ----------

New build with audio fix is posted and seems to work just fine.
[X 2014 Original Android Development] xdadevnube:
I'm not sure what the network fix that is being referred to, however, I have good news.

I confirm working data and CDMA voice calls on Verizon XT1096 16GB with 13R Baseband using CM-12.1 Official 09-11-15 Nightly.

I had tried builds as late as 09-06-15, and had no voice or data.

Awesome work guys!
[X 2014 Original Android Development] tacosrdelicioso:
The network fix was working voice and data for 32gb xt1096 and apparently some 16gb versions as well......
[X 2014 Original Android Development] iron maiden:
What gapps using?? Thanks very you

Regards
[X 2014 Original Android Development] nanca:
I like this one http://xdaforums.com/android/software/tk-gapps-t3116347

I prefer the pico modular package > proper dpi (lightest one) installs only core functions. No unnecessary apps.
[X 2014 Original Android Development] iron maiden:
Hello, very thanks..

regards...
[X 2014 Original Android Development] Tommebaas:
The bass sounds great in the latest nightly! Makes listening to music enjoyable again.

Sent from my Moto X
[X 2014 Original Android Development] kokotron:
But does the rotation vector sensor work? [emoji14]
[X 2014 Original Android Development] Tommebaas:
What's that?

Sent from my Moto X
[X 2014 Original Android Development] kokotron:
A sensor commonly used among astronomy apps. Try this app https://play.google.com/store/apps/details?id=com.calintat.sensors , select the rot. vector sensor from the left drawer, see if numbers change when you rotate phone.
[X 2014 Original Android Development] :
Rotation Vector

Apparently not working...

Does it require any particular system settings?
[X 2014 Original Android Development] halfsoul:
OK, Google works for me on any screen. Just verified from the xda app.

On 9/9 nightly.

However, Bluetooth connectivity is pretty poor. My phone no longer reconnects when I turn on my cars, Moto 360 frequently offline, etc.
[X 2014 Original Android Development] tacosrdelicioso:
Looks like I'm staying on mikeoswego's 9/10 build he made
[X 2014 Original Android Development] kokotron:
It shouldn't, it works out-of-the-box normally. Also it used to work in older CM builds during early July. I also thought this could be an xt1092 issue only but I see you have xt1097.
[X 2014 Original Android Development] adm1jtg:
Doesnt work on the xt1095 either
[X 2014 Original Android Development] G4 Man2:
Running a XT1097 that identifies as XT1095 because of properly converting and I have the same issue on the newest nightlies. That app you posted gives the same results but for the heck of it I ran a logcat and got this,

E/SensorService( 857): sensor batch failed 0xaec2ae00 30 0 200000000 0 err=Operation not permitted

When I switched the Rotation Vector tab.

Which a quick Google search let's me know you posted about the same error 5 days ago so this post is useless ¯\_(ツ)_/¯
[X 2014 Original Android Development] kokotron:
Ahahaha no it's not, it proves it's a legitimate issue :)
[X 2014 Original Android Development] mikeoswego:
The app shows not working on an xt1096 but Sky Map works..
[X 2014 Original Android Development] slogar25:
Yes as does CMs built in compass
[X 2014 Original Android Development] SurlyDuff:
Is anybody right now with an encrypted phone having an issue in recovery with new CM12.1 nightlies and TWRP 2.8.7.1? I switched to CM a few days ago from stock (factory reset and everything) and ever since, I've had an issue. It asks for my password upon booting to recovery (to decrypt the data partition), I input the correct password, but it tells me the password is incorrect and fails to mount.

I tried changing my password (to a word, a pattern, and a different PIN) but nothing allows me to mount the system partition in recovery. This also means I can't install updates the regular way since it can't boot to recovery and flash the update from /data. Apparently this was an issue a while ago with OPO devices but I haven't seen anybody talk about it with regard to the Moto X. Is anybody else with an encrypted partition having this issue or should I try a complete factory reset again to try to fix it?
[X 2014 Original Android Development] kokotron:
Sky maps, some compass apps and other older apps of similar functionality use a combination of other sensors to work (magnetometer, gyroscope etc).
[X 2014 Original Android Development] victor19:
Hey guys! Its the "no bass bug" fixed in the newest nightlies? No bass in songs, I mean.
[X 2014 Original Android Development] adm1jtg:
Been fixed since 9/11 build
[X 2014 Original Android Development] victor19:
Thanks bro!
[X 2014 Original Android Development] Fr0stbyteX:
It's a bug in TWRP for victara. Try using crpalmer's custom build. That seems to fix it.
[X 2014 Original Android Development] FreVDP:
Does anybody know what this is all about?
[X 2014 Original Android Development] crpalmer:
I think Dan was tidying up duplication and deduplicated a little too much thereby breaking the world. So he unbroke it before you all had a bad build.
[X 2014 Original Android Development] FreVDP:
[IMG="Gif"]http://img.pandawhale.com/67416-David-James-yes-not-bad-gif-re-Tei5.gif[/IMG]
[X 2014 Original Android Development] mikeoswego:
On Linux type systems the command issued to compile all the source codes into a new OS is "make buildworld". If there is something wrong with the sources and the compilation fails, then "world is broken." So he fixed a problem that was preventing the world (new rom) from compiling/building, he repaired or unbroke the world. (Android is Linux like but Google likes to be cute so "make buildworld" is replaced by "brunch victara" in our case.)
[X 2014 Original Android Development] mikeoswego:
Time stamps

When I reboot to recovery while running the Motorola ROM on the xt1096, the time in TWRP is correct. When I reboot while running CM, the time is off by a large amount into the past. This results in time stamps being wrong on backups. I know it is trivial but I'll post some TWRP log snippets here and maybe something will be obvious to someone more knowledgeable than me. I notice that TWRP got the time offset from different files but don't know why that would be. I might look around in the CM code for the ats_1 and ats_2 files. These logs where created about 20 minutes apart.

TWRP log after CM ROM with wrong time:

I:TWFunc::Fixup_Time: Pre-fix date and time: 1970-01-01--16-56-32
I:TWFunc::Fixup_Time: Setting time offset from file /sys/class/rtc/rtc0/since_epoch
I:TWFunc::Fixup_Time: will attempt to use the ats files now.
I:TWFunc::Fixup_Time: Setting time offset from file /data/time/ats_1, offset 1442300934236
I:TWFunc::Fixup_Time: Date and time corrected: 2015-09-16--00-05-26

TWRP log after Moto ROM with correct time:

I:TWFunc::Fixup_Time: Pre-fix date and time: 1970-01-01--16-39-11
I:TWFunc::Fixup_Time: Setting time offset from file /sys/class/rtc/rtc0/since_epoch
I:TWFunc::Fixup_Time: will attempt to use the ats files now.
I:TWFunc::Fixup_Time: Setting time offset from file /data/time/ats_2, offset 1442441804387
I:TWFunc::Fixup_Time: Date and time corrected: 2015-09-17--14-55-55
[X 2014 Original Android Development] SurlyDuff:
Thanks a bunch. Seems to be working:)