yashsingh1/xdaforums huggingface dataset:
[ONE General] Ok_Kaleidoscope5109:
You should not need to mess with mixers_paths.xml. That's more looking at the problem from a volume perspective. Just having OK Google not work doesn't imply its a volume issue. Can you be sure OK google is even listening? The best way to check is to add the Google Now widget.

After you do so, look carefully at the widget.

Does it look like this?

Or is the microphone icon on the right hollow?

The latter implies OK Google is not working at the moment, and can be caused by any number of reasons. Here are some questions to help you troubleshoot:

What launcher are you using?

Did you turn OK Google Voice detection on?

Regarding point #2, there is an option to turn it on from any screen too. Is that on?

What about the 3rd option that allows you to use Trusted Voice?
[ONE General] tijuanacartel:
thx for the PM...

I can't even complete the OK Google training. I can get one "tick", but no more.

I tested on phone calls this morning and I can only be heard if i use speaker phone. But, Viber works fine :( Also, google voice search works if i hit the microphone button.
[ONE General] NWKENT:
Your welcome..try as user post # 3470..

sent by my: SandStone Black 1+1

(aka) OnePlus One, OPO (Device ee)
[ONE General] xzaxox:
Okay. I am glad that it is rom related and not hardware issue :o
[ONE General] highdiver_2000:
Please check if you are using English US everywhere. That usually fix it for me.
[ONE General] hogze94:
doesnt look like todays build will be successful?
[ONE General] fmc000:
Failed exactly like yesterday.
[ONE General] hogze94:
I assume it's the same bug since the 4th? Wonder how long it will be fixed, then we can find out whether the kernel commits will fix the reboot issue.
[ONE General] fmc000:
Since yesterday, there was no scheduled build for the 5th. Last time this happened it took them 4-5 days.
[ONE General] LeroViten:
[MENTION=5411589]giaur[/MENTION] did you manage to compile your own build lately? ;)

Sent via OnePlus One
[ONE General] :
It's fresh and from [MENTION=286165]eris23[/MENTION]

https://www.androidfilehost.com/?fid=24052804347769913

Gesendet von meinem A0001 mit Tapatalk
[ONE General] Spannaa:
I'm not [MENTION=5411589]giaur[/MENTION] but if you want an unofficial nightly that is completely stock, [MENTION=286165]eris23[/MENTION] has just uploaded cm-12.1-20150707-UNOFFICIAL-bacon.zip

You'll need to flash the 20150505 firmware first though (but you can go back to the 20150515 firmware afterwards if you like).

Downloading it now...

[EDIT] Beaten to it by [MENTION=2044343]accuphase[/MENTION] [/EDIT]
[ONE General] fmc000:
Is this just a clean build? Do you know the last changeset it's based?
[ONE General] :
It's clean, more details are directly above your post

Gesendet von meinem A0001 mit Tapatalk
[ONE General] fmc000:
The changeset is not there, actually, but thanks anyway.
[ONE General] eris23:
My builds are pure cm stock. I'm running the 20160707 build on my OnePlus right now. I wish cm would fix their updater-script and/or updater-binary regarding the firmware issue. I don't want to disable the relevant line in case someone tries to install over pre-0109 trustzone firmware.

I usually sync about 4 or 5 hours later than cm builds.
[ONE General] neelgangrade:
This baby got delivered yesterday !! i exchanged it with HTC DROID DNA and got it in $199 64GB Sandstone black ! :D

Since i was previously working on CM based ROMS, i am still learning for OPO ! can anyone give me quick response for this question ?

Does boot.img is required to flash everytime via CMD ? like the same way in HTC phones ?

Does the camera app in NIGHTLIES is same as in official 5.0.1 ? Or its a stock CM camera app ?

Will appreciate if someone can reply.

Thanks !! ROMS Coming soon ;)
[ONE General] Spannaa:
If you want to use a custom kernel, you'll need to re-flash this after flashing a new nightly.

The camera app included is stock CM but the CM OS12 camera (CameraNext) will work on the nightlies if you include the lib files.

There's a flashable zip here that includes the lib files and an addon.d sh script that'll backup and restore everything when you flash a new nightly.
[ONE General] giaur:
No, I didn't now I'm looking for a way to make cabc disabled by default
[ONE General] Wrexthor:
I just got my OPO running again after being without it for over a month. Im running 5.0.2 stock CM now.

Are there still problems with 5.1 builds? (touchscreen, battery, wifiproblems etc). I want a rom with as few bugs as possible but like some of the new 5.1 features (ran it before my OPO broke).

Not sure if i should stay on 5.02 or upgrade to a newer one, don't really want to troubleshoot any more problems for a while now.
[ONE General] novren:
No need for the lib files, already included in the nightlies. Just need to install the apk, just gotta search on Google
[ONE General] fmc000:
You sure about the libs? Because I can't find them in /system/lib .
[ONE General] AcmE85:
You're right, the libs aren't included.

But the modded camera next includes them inside the apk.

I guess if you want to use the unmodded apk you need to flash the libs

for the panorama mode to work. Everything else runs fine.
[ONE General] Spannaa:
libjni_tinyplanet.so is included but the stock CameraNext needs libjni_tinyplanet_next.so &

libjni_mosaic_next.so which aren't.

True, but the original question was about the stock CameraNext app

Sent via Bacon...
[ONE General] wild1z:
Dude, put DOS on it. Trouble free! :cool:

Or, install 5.02 again with xposed?

Or, just dive in and try it? I don't have any issues after reading the last 20 pages and trouble shooting for my set up. It's all good! Good luck!
[ONE General] NWKENT:
Do a clean install, flash the latest "Nightly" 0704, leave STOCK kernel, with exception of Xposed, Gravity Box and a few themes, and enjoy your device, Dont tweak, leave that to the Dev's per Nightly..

Absolutely NO complaints with Nightlies for the past couple month's, a hic-up ot two, but nothing serious..Have flashed almost every Nightly since May..SOT on one of my SandStone Black's, with CM12.1, 5.0 - 5.5 hours, with data, GPS active the complete cycle..I NEVER turn off data (or) GPS, on 24/7..

sent by my: SandStone Black 1+1

(aka) OnePlus One, OPO (Device ee)
[ONE General] tiny4579:
And others have had force closes, crashes, reboots, and maybe issues where the screen wouldn't wake.

My advice is stay where you are or try sultans builds. The nightlies still aren't where they should be.
[ONE General] karangupta:
I did some search and found this, I think this would help you!

Here : http://xdaforums.com/showpost.php?p=55129456&postcount=667

---------- Post added at 09:39 PM ---------- Previous post was at 09:33 PM ----------

Finally there's a commit that could solve the mic gain problem on the camera video recording!

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

A ray of hope after almost a year! Jira (BACON-64)
[ONE General] red.Wood:
Anyone know where I can find the CyanogenMail by Boxer on the original version? Need exchange.
[ONE General] giaur:
No, I mean how to configure kernel before compilation to get cabc always disabled
[ONE General] karangupta:
I don't know much about ROM compilations but I think you can add a script which runs this code as soon as the ROM gets flashed. Or maybe a startup script that would run the first time the phone boots.
[ONE General] Donald Nice:
Use gmail or stock email app, both can exchange, depending on gapps you are using. Boxer is closed source.

Gesendet von meinem A0001 mit Tapatalk
[ONE General] spyd4r:
anyway to making the ringing volume while on speakerphone even remotely audible? voice is low, but bearable.. but the ringing noise I cannot hear at all. volume is terrible with speakerphone in general.
[ONE General] giaur:
Yes I know, but when building it by myself, I'm pretty sure I can disable it permanently and no scripts will be needed anymore

---------- Post added at 09:15 PM ---------- Previous post was at 09:10 PM ----------

http://www.apkmirror.com/apk/boxer/...il-2-0-0-cyanogen-os-12-android-apk-download/

https://play.google.com/store/apps/details?id=com.boxer.email
[ONE General] mkrogh65:
Absolutely agree ....

installed latest "Nightly" 0704, ... Clean install ... setup my apps after.... no tinkering with kernel or other stuff...

Having used this for 2 days, and have had several reboots, call drops, and odd behavior....

Man I think im rolling my cm12s backup in again -

This CM12 is really not ready yet :(
[ONE General] tijuanacartel:
After messing with mixer_paths.xml google is working!

Unfortunately still nobody can hear me in call. Viber works perfectly though :confused:
[ONE General] red.Wood:
Thank you both, but my work mail is restricted to only 3 apps. Boxer, Nine and the stock email app which doesn't come included anymore and I can't find anywhere. The Cyanogenmail app worked just fine as it was with boxer. Where can I find the latest stock email apk?
[ONE General] AcmE85:
It's still in the nightlies. Maybe your gapps package deletes it.
[ONE General] lordsinasina:
There you go : http://www.apkmirror.com/apk/google-inc/email/email-7-0-1669963-android-apk-download/
[ONE General] Ok_Kaleidoscope5109:
But why are you messing with mixer_paths.xml if you were originally using the cm12.1 file to begin with?
[ONE General] tijuanacartel:
So I looked at this http://xdaforums.com/oneplus-one/help/oxygen-os-speaker-output-louder-os-t3073916 and found that the mixer_paths.xml for Oxygen OS is substantially different to the one CM is using (https://raw.githubusercontent.com/C...e_oneplus_bacon/cm-12.1/audio/mixer_paths.xml)

This could be the root of my issue.

---------- Post added at 12:02 PM ---------- Previous post was at 12:01 PM ----------

Because nobody can hear me on call!

I suspect that all CM developers never actually use their phone as a phone :(
[ONE General] spyrale:
Have you tried turning off Ok Google everywhere?
[ONE General] tijuanacartel:
Yes I did, it made no difference.
[ONE General] Jur1nator:
Apparently today still not a new build :(

€: I stand corrected.. Downloading via cyan delta right now :)
[ONE General] Ok_Kaleidoscope5109:
Yeah but then no one would be able to use their phone too. I can bet you almost everyone here also makes phone calls. Have you tried a full wipe? Perhaps you have a defective mic.

I can understand tweaking with mixers_paths.xml if the volume is low for example, but you're saying OK Google does not work at all or calls don't work which leads me to believe it's something specific to your phone--either software or hardware that's causing trouble.
[ONE General] tijuanacartel:
I Really, Really doubt that it is a hardware issue since it works in Viber PERFECTLY. And, from googling around there are hundreds of users with this issue, though many of the posts date from last year.

This is my very first OPO rom and I formatted userdata from fastboot. Google voice search does work after editing the mixer_paths.xml, it is now only POTS voice calls that aren't working.

To clarify: "not working" means nobody on the remote end can hear me. Wired headset makes no difference. Speakerphone works fine.
[ONE General] fmc000:
Believe me, I use my OPO as my only phone and everyone can hear me during calls and I use the default mixer values on CM12.1 nightlies. It's not clearly a ROM problem but something on your side.
[ONE General] tijuanacartel:
Well I just did a factory reset and it is back to not working at all.

Maybe it is a flaw in certain phones using certain microphones that was worked around in Oxygen OS.

It's just too weird to me that it works in Viber (that's now the only way I can call my wife)
[ONE General] fmc000:
Did you restore apps or data? Did you flash anything else after the ROM? Did you wipe your system partition before flashing?
[ONE General] Ok_Kaleidoscope5109:
Factory reset in TWRP?
[ONE General] tijuanacartel:
Haven't flashed anything else and confirmed that the mixer_paths.xml is the same as the one in the git tree.

Anyone who has working microphone in calls, can you please make a call and take a logcat and let me know this line:

D/voice ( 384): start_call: enter usecase:voice-call

D/audio_hw_primary( 384): select_devices: out_snd_device(6: voice-handset) in_snd_device(55: voice-dmic-ef)

Thanks!

---------- Post added at 04:53 PM ---------- Previous post was at 04:38 PM ----------

Another question, for those for whom the microphone works in calls, is does your carrier support HD Voice?
[ONE General] Wrexthor:
Thank you! Was looking for honest advise. People tend to get flash-blinded and recommend anything even if there are bugs/crashes etc.
[ONE General] giaur:
Yes it does. HD Voice whithin the same carrier operator and when calling to user who has supported phone connected to 3G network.

And no voLTE support.
[ONE General] pijas82:
Cyandelta?!? :confused::confused::confused::confused::eek::eek::eek::eek::eek::eek: OMG loooooooooool

Sent from my A0001
[ONE General] fmc000:
What's so funny? It works perfectly and for example the today's delta was only about 25megs with four days of gap between consecutive nightlies. Much better than downloading about six times that much.
[ONE General] giaur:
100 Mbps connection in my case. Do you really think that I would bother, 25 megs, 250 megs, who cares? Simplest way, without any 3rd party apps
[ONE General] spyd4r:
i don't understand why you're bagging on cyandelta? I'd much prefer to download 10-25mb a day instead of like 250mb

---------- Post added at 10:57 AM ---------- Previous post was at 10:56 AM ----------

I find CyanDelta notifies of the update long before the OS even checks for an update.
[ONE General] fmc000:
I don't know if you bother or not, in my case with 4 Mbps this makes all the difference in the world. Moreover, even if it didn't make sense there's no reason to be so impolite against other users who find the app useful.
[ONE General] sheppy1:
Is it necessary for me to re-flash my kernel every time I update to the latest nightly of CM?
[ONE General] giaur:
I'm not impolite. By the way, cm should finally add incremental updates for nightlies
[ONE General] fmc000:
I'm not referring to you but to the guy that first bashed against cyandelta.
[ONE General] cgjjaf:
Did you find a solution to the NFC problem? I did a search on the web and nothing either.
[ONE General] nsmart:
I would recommend to stay with stock rom (Cyanogen OS12). When using nighlies for bacon you are in the test lab for stock rom. Stock rom has at least some kind of quality assurance by going through Google certification. It has it's bugs of course but there is more priority on stabilization. The circumstance that cyanogenmod did not release a snapshot build of cm12 / cm12.1 hints you at what they think about the stabilty of their rom themselves.
[ONE General] Ok_Kaleidoscope5109:
I'm not against patches, but patches are also how frequently you bloat up OS partitions and how you can result in a very flaky installation. I get it that everyone has flashaholic syndrome, but patch after patch after patch is exactly why you see some users here reporting random bugs that you will not get with a clean flash.
[ONE General] fmc000:
This is not how cyandelta works, BTW.
[ONE General] giaur:
What if I change something on system partition? For example, remove system app. Any incremental ota solution refuses to install update in this case. I remember some incremental update systems available in other popular custom roms (MoKee for example but not only).

CM update is always full, "patching system image unconditonally", so isn't it more safe?
[ONE General] tiny4579:
It's a full zip and system gets wiped whether you use a nightly zip or cyandelta. I don't know if firmware gets included. I don't believe it does though.
[ONE General] fmc000:
You clearly don't have the slightest idea on how cyandelta works, I see.

---------- Post added at 08:25 PM ---------- Previous post was at 08:24 PM ----------

yes it does.
[ONE General] tiny4579:
Derp. You're right. I shouldn't be assuming stuff. It makes sense the firmware is included as it basically creates a new zip based on what you have and the nightly which is pulled from cm. What gets downloaded then is a delta and then the full zip is built. Cyandelta is actually a good idea. I just prefer to directly pull nightly zips. I can't recall an issue that was tied to using cyandelta instead of a nightly zip.
[ONE General] giaur:
Ok, I see. So delta download, but as a result we will get full zip. But we need previous (full) zip already present to apply downloaded delta on it
[ONE General] fmc000:
The main issue is that cyandelta doesn't keep track of pulled nightlies. And a minor issue, that affects me BTW, is that it doesn't work well with PhilZ recovery.

---------- Post added at 09:45 PM ---------- Previous post was at 09:44 PM ----------

Exactly.
[ONE General] nigelhealy:
So my usual daily driver is a Nexus 5 (hand size single hand reasons when bike commuting) but I'm currently on 3 week move daily hike/camp/train/hobo trip and I shifted to my OPO as my daily device due to bigger screen and better battery and on these CM12.1 nightlies. I kept my N5 as fallback (e.g. if OPO got damaged).

OPO CM12.1 way too many bugs, just too many random reboots or phone not working. I tried the Sultrans version but was worse.

So I took a short non-moving day to downgrade to CM11S which was actually my most reliable build.

Unfortunately the flash hard bricked the OPO. I was looking at fallback to my N5 for days til I passed someone with a Win7 laptop and followed unbrick guides and now on OPO CM11S.

I have tried CM12S but was worse than CM11S so think I'll wait for CM12.1S which I read was due soon.

My theory is......the OPO build quality was lower and more wider variability of handsets than usual leading to wider variability of experiences on these CM12.1 nightlies each fighting for conclusions and just hard to drive to a focused stable version.

Some of us have been luckier than others.

My N5 on current 5.1.1 is 100% stable (but SOT sucks) and it takes a 6 month old 4.4.4 for OPO to be as stable.

I agree with the above that the lack of a Bacon CM12.1 stable is due acknowledgement of the plain facts.

The OPO experience has been good, performance reliability and it's solidified a OP2 / OPT decision but focused on the Android story.
[ONE General] ace_apr27:
Is the proximity sensor bug universal or does it affect only some devices? I'm facing multiple issues with my proximity sensor and I was wondering whether they're acknowledged bugs as I didn't see them in the list OP put up. The first bug is when the screen goes black and refuses to come on (till I connect either a Bluetooth or a wired headset, sometimes, not even then) as soon as I make or receive a call (making it impossible to answer the call, home button to answer doesn't work) and the second is that the screen will arbitrarily freeze when the phone is locked and the notification LED will blink fast (just as it does When you have a missed call or when your battery is low) but the color will depend on the notification that's presently there. The lock screen gestures are iffy as well and don't ALWAYS work. The screen comes on randomly if I keep the phone on my pocket, screen facing towards my leg and not "outward" (if that makes any sense). Also, if I use a headset to answer a call the screen won't shut off after I disconnect. It remains at this weird, partial brightest state (almost like a screen filter is applied) but is unresponsive till I press the power button., which brings it to normal brightness and makes it responsive. If I don't do this, then the screen stays in this half lut state, the battery starts draining like mad and the phone heats up. Speaking of which, it's been heating up like crazy after some of the latest nightlies. I am so experiencing quite a bit of lag, specially when playing games such as Ingress (thermal throttling could be the culprit).

Is there anyone else who has these issues? Are they common? Are there any fixes?
[ONE General] giaur:
So, I'm really lucky. No reboots at all. No noticeable bugs.
[ONE General] nigelhealy:
My handset was a 2nd batch July, so early, but not the first batch, about to drift out of warranty.

If someone had the time I betya there is a correlation between handset build date and which CM works best.
[ONE General] Dzhedaj:
In regards to the proximity sensor, the only issue I face with the latest few nightlies is it's being cheked on screen unlock, but ignored. So prevent accidental wake up doesn't work, can't put the phone in my pocket...
[ONE General] AcmE85:
I used to have this a couple days ago, but it just fixed itself. Don't ask me how, I did not even reboot.
[ONE General] fmc000:
For me the nightlies are perfectly stable, The phone quality is pretty good and the proximity sensor works like a charm. The only bug I have is the compass totally unreliable.
[ONE General] 99x:
Stability isn't an issue for me, battery is just so much better on CM11S, especially when on mobile data. 5-6 hours SOT compared to 3-4, exactly the same apps and usage pattern
[ONE General] droidnext:
The problem is that you come back and forth between cm11 and cm12 based roms, so your modem is broken. You can fix it by clean install (wipe everything including internal sdcard). Use the original image, not the flashable zip. You can install by Wug's toolkit or fastboot command.
[ONE General] Ok_Kaleidoscope5109:
Can you explain how the modem is broken if modem is flashed during a CM install? A factory reset does nothing to reset the modem and that's what I did coming from CM11 to 12.1 My proximity sensor works to prevent accidental wakeups but does not work during calls. Does everyone else's proximity sensor work in call?
[ONE General] novren:
Flashed last nightly with full download (using cm downloader app) and new tk gapps, battery life is superb and no reboots.
[ONE General] tiny4579:
Factory reset won't fix the modem, completely unrelated. Modem is flashed with nightlies. So to revert back to cm11 it'd make more sense to re-flash the ROM if a nandroid is taken.
[ONE General] Ok_Kaleidoscope5109:
I understand that. I'm referring to this post that claims the modem is broken because [MENTION=4670577]ace_apr27[/MENTION] is going back and forth between CM11 and 12. I have done that too, but I'm failing to understand how the modem would be broken. Furthermore, [MENTION=4718366]droidnext[/MENTION] suggests doing a full wipe which is what I've done as well, but I fail to see how that addresses the modem if indeed the modem is broken.

If you really want to wipe the modem and start fresh, it'd probably be best to use fastboot to wipe the radio and write a new radio to it. That's why I'm trying to understand if my experience with the proximity sensor during calls is completely out of whack or are other people seeing that too.

For the record my proximity sensor worked fine in CM11 last week.
[ONE General] TorchaOne:
Flashed without gapps and almost all accounts gone and gapps too. Superb.
[ONE General] ace_apr27:
But I DON'T got back and forth between CM11 and CM12.1. I never said I did :/

I've read that screen guards can cause proximity sensor issues but I don't have one that covers the proximity sensor.
[ONE General] dnle71:
0708 nightly stanby is drains faster than 0704
[ONE General] AcmE85:
So the gapp's backup script did not work. Which gapps are you using?

This happened to me once with slim gapps a couple weeks ago and was

due to a faulty backup script -> blame gapps
[ONE General] TorchaOne:
Opengapps, I had 07/07 version. I had to restore BU and then rom+gapps and all good. This was second time for me, first happened with other gapps. Open gapps has been working otherwise nicely and so on. Have to check their thread.