yashsingh1/xdaforums huggingface dataset:
[X 2014 Original Android Development] tacosrdelicioso:
Took a gander at the code looks like an attempted fix has been implemented
[X 2014 Original Android Development] Nebelschwaden:
4G connection

I hope anyone can help me out with my issue.

First of all, I am on the 20150827 nightly with stock kernel.

I have flashed CyanogenMod on my XT1092 (Europe, directly purchased from Motorola via Amazon). Since then the devices model changed to XT1095 in the about phone section. The issue I encounter is the lack of 4G/LTE connectivity. The best I can get to is HSDPA.

So I downloaded the stock XT1092 firmware (Android 5.1) for my device (location: Germany) and extracted the fsg and non-hlos files and flashed them in fastboot via adb. I also erased the modemst1 and modemst2.

I did a factory reset and dalvik / cache wipe before.

But in fact nothing has changed! The situation remained just the same as before.

Do you guys have any idea?

Also: Will I need to re-flash the modem files after I update to a new nightly (I update using cyan delta updater)?

Thanks in advance!
[X 2014 Original Android Development] Aroch925:
Just tried the new build from today. It didn't fix the problem
[X 2014 Original Android Development] tacosrdelicioso:
No sim no baseband issue remains

Logs

https://drive.google.com/file/d/0B-...nFmRDJDbURwMDlxdVFyR3lR/view?usp=docslist_api
[X 2014 Original Android Development] adm1jtg:
I thought the changes for xt1096 were in the 8/30 build which never posted
[X 2014 Original Android Development] Aroch925:
It was included in the 8/31 which was posted
[X 2014 Original Android Development] invisiblek:
Very weird. I find it extremely odd that some XT1096s work (like mine) and others don't.

<3>[ 6.910848,0] SMSM: Modem SMSM state changed to SMSM_RESET.
<3>[ 6.910979,1] Notify: start reset
<3>[ 6.910987,0] Fatal error on the modem.
<3>[ 6.910999,0] modem subsystem failure reason: fs_device_efs_rmts.c:154:[8 ,1572864, 1] EFS: rmts_get_buffer api failed.

Still looking into it...
[X 2014 Original Android Development] slogar25:
Did you ever encrypt your sim? Or any kind of encryption
[X 2014 Original Android Development] AntsInMyPants:
Yes, very frustrating. I have tried everything with no success. The SIM card works fine with 5.1 stock as well as every ROM I throw at it on my N6.

I would be more than happy to loan you my XT1096 if that would help. It is a spare phone and I can get by without it for a bit.
[X 2014 Original Android Development] invisiblek:
That'd work, but before we go through all that, I want to check a few things. I'm still leaning toward this being a mismatched firmware or something odd. Here is a listing of all the md5sums of all the files in my /firmware, /fsg, and /persist partitions. Can you check yours against them?

https://gist.github.com/a091599be65025495a2e

(hint: from an adb shell: md5sum `find /persist -type f` ) (that's a backtick, the other character on your tilde button)
[X 2014 Original Android Development] Aroch925:
Other than the lockscreen password, no
[X 2014 Original Android Development] AntsInMyPants:
I don't have my XT1096 with me at work so I won't be able to do anything until this evening.

If someone else who is having the SIM issue can try this it would help speed things up.
[X 2014 Original Android Development] adm1jtg:
Reading the cyanogenmod docs it says the snapshots are usually 2 weeks behind weeklies. Is This the case for the current monthly for our victara as we have had a lot of pretty major changes in the last 2 weeks. Trying to figure out if things like the updated moto blobs are in the current snapshot.

Course it also says snapshots should be monthly and as far as i can tell thats not true for 12.1 as this looks to be the first shanpshot ever for 12.1 for victara and in fact only the third one for any OS.
[X 2014 Original Android Development] Aroch925:
I should be home around 2:30. I'll do it then
[X 2014 Original Android Development] felipevsw:
I was actually curious about the 2 snapshots and one being considerably bigger than the other. Any thoughts?
[X 2014 Original Android Development] adm1jtg:
Based on the naming one is cm12 aka lollipop 5.0 base and one is cm12.1 aka lollipop 5.1 base

And I was told in the cm irc channel the snapshot is from code over a month old. For me when I load it phone fc's continuously. I am sure if I cleared data it would be fine but just not willing to put forth all that effort.
[X 2014 Original Android Development] Aroch925:
Here's the partitions. It seems like the differences are in the persist partition.

https://drive.google.com/file/d/0B6kWVVJhYz9KbTZUNHJmOE9XckE/view?usp=sharing
[X 2014 Original Android Development] Tinchoska:
Guys, are this releases or the latest snapshot release is with this caf patch?

Enviado desde mi SM-T700 mediante Tapatalk
[X 2014 Original Android Development] t3chn0s1s:
http://www.cyanogenmod.org/blog/releases-releases-releases-august-2015
[X 2014 Original Android Development] G4 Man2:
http://review.cyanogenmod.com/107964

welp, good luck to everyone I've seen complain about audio issues on this thread.
[X 2014 Original Android Development] mikeoswego:
I thought he was saying the problem with AudioFX was in the offloading so he is disabling offloading to allow AudioFX to work until someone else has time to look into the offloading issue. I guess we'll see once the next build is available.
[X 2014 Original Android Development] adm1jtg:
Hopefully someone in here who is smarter then me can tell me exactly which files to replace to get this one set of changes into my snapshot build. AKA make an update zip or tell me exactly which files to move manually so the sound issue is patched.

http://review.cyanogenmod.org/#/c/107964/

Update: NM figured it out myself

Update2: Manually made the changes listed above then loaded v4a and now sound is great... it didnt work at all before i made those changes.
[X 2014 Original Android Development] 0.0:
Does the "ok, Google" hotword from any screen work?

sent from my Moto X Pure Edition
[X 2014 Original Android Development] ilmorga:
Not for me.

Inviato dal mio XT1095 utilizzando Tapatalk
[X 2014 Original Android Development] 0.0:
So I am not the only one. I remember it was working a few days before. [MENTION=3857343]crpalmer[/MENTION] or anyone who may know, what controls Google Now's hotword on any screen? frameworks_av? Is it device specific?
[X 2014 Original Android Development] tyus2:
The Ambient Display doesn't seem to work in the latest build - September 2, 2015 build. Can anybody confirm?
[X 2014 Original Android Development] nanca:
Working fine for me. Did a clean install!
[X 2014 Original Android Development] 0.0:
I did a clean flash to see if the "Ok, Google" hotword from any screen. It didn't work still. It only works in the Google Now app. I also did a clean flash on my Nexus 7, and "Ok, Google" hotword works on any screen
[X 2014 Original Android Development] mikeoswego:
Just for the record, on the stock ROM (xt1096) with Moto Voice deactivated and using the Google Now Launcher, OK Google does work on home screens but not while any app is open or with screen off while charging even though that is enabled in settings. Using Trebuchet instead of GNL results in OK Google only working on the Google Now app page.
[X 2014 Original Android Development] 0.0:
"Ok, Google" on any screen was working a few nightlies before. I'm not sure if a commit caused it to break and if so, I want to revert it

sent from my Moto X Pure Edition
[X 2014 Original Android Development] dg4prez:
Anyone experience mobile networks shutting off for no reason? Latest nightly.
[X 2014 Original Android Development] mikeoswego:
I guess I was wondering if it was actually a change in the Google app that caused this. Then there is the adding of the "victara: add motorola-specific play store props and permissions" in the 08/27 nightly that might let the Google App "see" that it is a Moto X and change it's behavior. Or maybe the commit "Add Hotword audio capture constants" for the next nightly is the ticket.

I'm just rambling here because I remember on the 1st gen Moto X, the Google app wouldn't even turn on the voice detection on the stock rom but would on the CM rom. I know, apples and oranges, probably.
[X 2014 Original Android Development] 0.0:
You make a good point, so I may end up reverting that commit, since it could be the culprit. The other commit about adding hotword audio capture is for cmsdk, so it allows devs to utilize that constant. I cherry-picked it and it didn't work
[X 2014 Original Android Development] Aroch925:
Any update on the xt1096 sim problem? I also found that when I have CM on my phone it wont stay off. Ill turn it off and if I let it sit for a few seconds it jus turns back on. I dont know if this has anything to do with the sim problem but I figure I'd tell you guys all the problems just in case
[X 2014 Original Android Development] AntsInMyPants:
My XT1096 is on it's way to Invisiblek so hopefully he will be able to figure out what is going on.
[X 2014 Original Android Development] Tommebaas:
Does anyone know anything about the sound and music issue?

Has it been fixed in the last nightlies?

Sent from my Moto X
[X 2014 Original Android Development] Tommebaas:
What did you do exactly?

I want to do it myself also.
[X 2014 Original Android Development] 0.0:
What'd you do? What files need to be moved around?

sent from my Moto X Pure Edition
[X 2014 Original Android Development] adm1jtg:
None actually, Since I wanted to stay on snapshot and the above commit was not pushed till after the snapshot released I made all the changes manually to the audio.conf and build.prop and the loaded up viper_v2.3.4.0_-_remove_fx_build_fix

Sound is drastically improved for me. Is it completely fixed.... I don't think so occasionally some songs still sound horrible but most sound like they should now.

Still continuing to try different configs and files but this is the best i have found so far. I would suspect perhaps one of the hardware libs files for audio was somehow changed but am not enough of a dev to know which. Am working on getting an older version of remix or cm12.1 that does not have the sound issue and doing a massive compare of file sizes hoping that may shed some light on things but no one seems to know when the sound issue began and worse then that no one seems to have and be willing to post a copy of the older version that worked properly.

Just to save duplicate work I have tried using dspmanager a few versions and played with all the files in soundfx as well as an audiofx fix i found.
[X 2014 Original Android Development] adm1jtg:
Can you tell me when your sound became bad was it on the build from the 22nd when you posted this or was it earlier? If earlier can you remember the last build that the sound WAS NOT an issue and maybe even post that build if you still have it. Yours is the first post I see in here related to the sound issues.

Thanks
[X 2014 Original Android Development] Tommebaas:
I think it was from the 16th nightly or something.

Sent from my Moto X
[X 2014 Original Android Development] Alexx_lml:
It was from the Nightly from August 1, 2015.

From this build it is that I started having problems with the sound, in fact I can not download old nightlys of July.

I had to use another custom rom the nightly wearing of July 27, 2015, that's where I have no problem, as I said before, it's since they started adding binaries rom stock of Motorola.
[X 2014 Original Android Development] 0.0:
Per request of [MENTION=2781850]adm1jtg[/MENTION], I reverted a commit that is related to sound and maybe it might fix the sound issue. The commit reverted is https://github.com/CyanogenMod/andr...mmit/9e79650c04f7d0cdd3bc1faffe108464183a83f9. Place files in the correct location
[X 2014 Original Android Development] Gafanhotz:
Did you reverted the entire commit? Because compressing offload is known of causing random reboots.
[X 2014 Original Android Development] 0.0:
Only that commit. I made sure that compressing offload was also removed and everything matched the other commits that are merged
[X 2014 Original Android Development] adm1jtg:
Can you confirm or deny that the audio_effects.conf file is the exact same in system/etc and in vendor/etc. Not sure if we need to just put those 4 files into system/etc or if we also need to place the audio_effects.conf file into vendor/etc as well.

Edit: Not where I can test atm can someone let me know results positive or negative.
[X 2014 Original Android Development] 0.0:
What you can do is on the current build, compare both files in those locations. If they look exactly the same, then I assume the files I posted will need to be moved to those locations as well.

I did not build the ROM, so I did not check. I just grabbed them from its location. When I build, I will end up uploading it to the temasek thread
[X 2014 Original Android Development] adm1jtg:
A very quick look and they APPEAR to be the same, same filesize and same beginning and ending lines

Ok so for anyone following this, download the files above, copy all 4 files into system/etc, then also copy JUST the audio_effects.conf into vendor/etc, reboot, test and please post results (Positive or Negative). I will try and test as well just wont be able to for a few hours at least.
[X 2014 Original Android Development] nithin1992:
I've made the changes according to the zip posted by [MENTION=2281583]0.0[/MENTION], everything seems to be working fine so far in case anyone was wondering if it works.
[X 2014 Original Android Development] 0.0:
Is sound back to how it was? I don't really know how it was supposed to sound
[X 2014 Original Android Development] adm1jtg:
Please read below, make the proposed changes and let me know if this helps. As always make a FULL backup first

---------- Post added at 05:48 AM ---------- Previous post was at 05:47 AM ----------

It was supposed to make the sound go back to "normal", without those changes many have said the sound was without bass
[X 2014 Original Android Development] kokotron:
Anyone on the 12.1 Snapshot on xt1092 can verify if the Rotation Vector sensor has been fixed?

EDIT: Nevermind, I tried it myself and it doesn't work. Where can I report things like this for Releases?
[X 2014 Original Android Development] bira792:
I wonder if this build has been fixed for my device is a victara xt1097.estar come as a xt1095.desde already agradesco.
[X 2014 Original Android Development] tyus2:
BUG 1: Audio recording in camera not stereo, also, bad quality.

BUG 2: Audio output from phone has no bass, bad quality.
[X 2014 Original Android Development] nithin1992:
Same here, I don't feel any noticeable change in comparison to how it was before. I guess someone else will have to test and report back. I just wanted to let people know that its okay to give it a try, doesn't break anything.
[X 2014 Original Android Development] adm1jtg:
Is this AFTER applying the above sound files? Also what build?
[X 2014 Original Android Development] tyus2:
Sorry. I have the build 03-09-15. I haven't applied the above files. I am searching the stock ROM for a fix. I'll upload to XDA if I get the sound back to what it was before.
[X 2014 Original Android Development] Gafanhotz:
Não tem problema em vir como XT1095, são os mesmos aparelhos. Não existe o que consertar. Tudo funciona.
[X 2014 Original Android Development] adm1jtg:
Try the above files they should resolve your sound issues
[X 2014 Original Android Development] tyus2:
OK. I will.
[X 2014 Original Android Development] :
So is it the kernel that has to support manual camera features? Can they be added by CM devs, or can they only be added by Motorola?

View attachment 3463944
[X 2014 Original Android Development] tyus2:
I can confirm the fix for audio doesn't work for me. Some other ROMs that are based on CM, but are a few weeks old don't have the sound issue.
[X 2014 Original Android Development] adm1jtg:
Can you try one more thing for me then... Look in your build.Prop and see if you have a #media section if your do remove all the lines in that section and reboot to test again.

Also are you an xt1095 if not what model as I am testing on my xt1095 and sound was better though I admit my ears are old so likely not the best judge

Appreciate all your help
[X 2014 Original Android Development] tyus2:
I use xt1092. The bass was not present, and there was some kind of distortion present, and I know this because there's virtually no difference between sound output from my pc and phone. Unfortunately, I cannot test your method right now, I am on stock rom, because I take my phone to my college and I listen to some music. And I can say, the sound is back to normal.
[X 2014 Original Android Development] nithin1992:
Yeah, just moved to stock to test it out, and there's a lot of difference between the stock and CM based ROMs. The stock ROM sounds so much better now that I hear it
[X 2014 Original Android Development] Gafanhotz:
Only by Moto. If ever. They didn't added that even to the new X and G.
[X 2014 Original Android Development] adm1jtg:
You willing to test a new build for sound quality or are you staying on stock
[X 2014 Original Android Development] dwiedunia:
try viper4android ;)
[X 2014 Original Android Development] nithin1992:
So I've moved to stock and I find the difference in audio too. Just play any song or video on loudspeaker or over the headphones and you'll easily get to hear it. I didn't think there was much wrong with the audio before, but I saw all these people complaining, then when I tested it out myself I see it now. If you have another Moto X around you could play them side by side or, play the song on CM and stock measure the sound output from an other phone via an app .

Not right now, I'm testing something for someone else on stock but I'm sure many here are ready to give it a try
[X 2014 Original Android Development] xdadevnube:
Sorry if this is a nube question.

What is the MR1 Gapps compared to Gapps that doesn't have MR1 in the filename?

I wanted to use Minimal Gapps (gapps-5.1.x-20150404-minimal-edition-signed.zip), would that be okay?
[X 2014 Original Android Development] xdadevnube:
I have XT1096. I just rooted, sunshined, installed twrp, install latest nightly, updated baseband to 13R

...and I can't get this thing to connect to the VZW cellular network. It would seem I'm having the same issue as the other people here with the phone not connecting. I tried two active SIM cards to no avail.
[X 2014 Original Android Development] Tommebaas:
I will test it. What build should I install?

Sent from my Moto X
[X 2014 Original Android Development] adm1jtg:
Check your pm
[X 2014 Original Android Development] crpalmer:
I think I know what is wrong with the audio. I will try to get it fixed tonight.
[X 2014 Original Android Development] vista178:
I believe a xt1096 is on its way to a dev to figure out what's up with our radios.
[X 2014 Original Android Development] zander21510:
Have there been any recent changes in the nightlies that have messed with the text message database or stock keyboard? My Textra app keeps freezing every so often since its last update (coincidentally on the same day I updated my nightly). Just trying to narrow down the issue cause.
[X 2014 Original Android Development] Munns86:
If you need one to test it let me know.
[X 2014 Original Android Development] adm1jtg:
Dont see anything in proposed changes for next build related to audio... yet
[X 2014 Original Android Development] vista178:
Our dev probably is going to build outside of the common channel, just an assumption on my part.
[X 2014 Original Android Development] adm1jtg:
Very possible, just anxiously awaiting something to test and curious to see what the issue was....

Also has the ok google issue been resolved?
[X 2014 Original Android Development] 0.0:
Commit for audio fix: http://review.cyanogenmod.org/#/c/108915/

I filed a bug report on jira for ok, google a few days ago, so I am still waiting on that
[X 2014 Original Android Development] invisiblek:
is anyone on an xt1096 having issues with the radio not working on a 16gb model or is this problem specific to the 32gb models?
[X 2014 Original Android Development] adm1jtg:
Yup saw the commit and already manually edited and applied the file :D but i wasnt having huge issues in the first place so not sure if it works.... Wanna test? or wait like the rest for the build to drop :D
[X 2014 Original Android Development] vista178:
I have the radio issue and have the 32GB model.
[X 2014 Original Android Development] Aroch925:
Mines the 32gb
[X 2014 Original Android Development] tacosrdelicioso:
I also have the 32
[X 2014 Original Android Development] mikeoswego:
Radios are good on my 16gb model if you want that data point.
[X 2014 Original Android Development] kokotron:
Rotation Vector sensor update.

Hello it's me again, the guy annoying you with the banal Rotation Vector issue. The issue is that this sensor, which is used in many astronomy applications, has not been working in any builds for the last couple of months. You can verify if it works on your device by downloading an app such as "Sensors" from play store. My device is the xt1092, though CM now reports it as xt1095. Early July builds didn't have the issue, but I don't remember if the device was reported as otherwise.

I tried to "debug" it myself using Android Studio logcat, what I got was a simple error message when I switched to the sensor in the Sensors application. The error was the following:

If someone could point me to a direction where I can research more about it, I'd be happy to hear.

UPDATE: I should also note that in the Sensors app, the specific sensor is reported to be made by Motorola. If my xt1092 is being registered as xt1095 (which is Pure Edition as far as I know), maybe there's a driver conflict here. If someone has an actual xt1095 model, they could check if the sensor has a different manufacturer. Of course this is pure speculation and may be based on misknowledge.
[X 2014 Original Android Development] 0.0:
I tested, and comparing to stock ROM, bass is not as strong
[X 2014 Original Android Development] slogar25:
I have the 16GB model and have always had working data and cellular on vzw with cm, however I tried the latest build of pa and got 3g only. Had to completely flash back to stock and re format internal storage with the stock recovery. Flashed CM again and have working lte data and cellular.

Another thought, the first time booting into twrp after a fresh flash it will ask if you want to keep system r/o. Could that have anything to do with radios not working with a custom rom?
[X 2014 Original Android Development] invisiblek:
Ok, so I'm going to call my assumptions from last night confirmed. At least I have something to go on...

I had this happen to me last weekend too and issuing these from fastboot cleared it up:

fastboot erase modemst1
fastboot erase modemst2

I doubt it. Its failing to finish firing up the modem. I fastboot flashed the 5.1 system and boot partitions that I dumped from my 16gb xt1096 before going to CM on to this 32gb one that was sent to me and radio was working. Something within our ROM isn't quite right. I have a few things I'm planning to try tonight.
[X 2014 Original Android Development] invisiblek:
The xt1092/xt1095 thing is purely cosmetic. I can fix it if you get me the output of:

adb shell getprop

Mine (xt1096) shows as a Motorola for the Rotation Vector as well. I'll do some digging on this...
[X 2014 Original Android Development] slogar25:
I had this happen to me last weekend too and issuing these from fastboot cleared it up:

fastboot erase modemst1
fastboot erase modemst2

Oh nice!! I guess I panicked lol.

I doubt it. Its failing to finish firing up the modem. I fastboot flashed the 5.1 system and boot partitions that I dumped from my 16gb xt1096 before going to CM on to this 32gb one that was sent to me and radio was working. Something within our ROM isn't quite right. I have a few things I'm planning to try tonight.[/QUOTE]

I thought it might be far fetched just was thinking maybe write protect had something to do with it