yashsingh1/xdaforums huggingface dataset:
[OnePlus X Original Android Development] CertifiedBlyndGuy:
Smart lock isnt working in 9.0s. I believe it did on 8.0s (however I did just finish testing CM 13). Besides that it's great. I did clean flash by the way.

---------- Post added at 02:50 AM ---------- Previous post was at 02:28 AM ----------

Nope.

Oh, and hangouts dialer crashes as well. I'm sure it's related to the listed bugs though on the OP
[OnePlus X Original Android Development] sankarshan:
I can confirm that smartlock is working in 8.0s
[OnePlus X Original Android Development] ravinder0003:
Bro speaker mic isn't working in v9 too...
[OnePlus X Original Android Development] Willykit:
Ok, I followed your advice and I completely wiped my phone, including data. I then flashed v.8 but the volume problem persists. I 'm running out of options here!
[OnePlus X Original Android Development] dragan012:
Unfortunately I can confirm speaker mic is only working after applying Fix zip even after upgrade to v9.0....:(
[OnePlus X Original Android Development] ravinder0003:
After the fix it will work... But as op asked i was confirming that it still doesn't work without that zip..

So you also have echo?
[OnePlus X Original Android Development] dragan012:
No, I do not have echo on my device
[OnePlus X Original Android Development] Sundar1995:
I cleaned flashed 9.0

Didn't have echo problem and not having it now also

Mic on speaker is not working on calls and sound is low on speaker.

Haven't applied the fix yet
[OnePlus X Original Android Development] RinoFxx:
I cleaned flash 9.0 too! No echo found! Everything is faster and smoother than oxygen! Very good work!! Only one thing! I don't know which version of xposed to flash for this device..i'm not expert..any help?

Inviato dal mio ONE E1003 utilizzando Tapatalk
[OnePlus X Original Android Development] dtosun:
Please be carefull, echo is not your voice, it is other side's voice.
[OnePlus X Original Android Development] parasthakur37:
Yes the other person will hear his/her voice again. Echo.
[OnePlus X Original Android Development] TikiThePug:
Flash xposed-v79-sdk22-arm.zip from here: http://xdaforums.com/showthread.php?t=3034811
[OnePlus X Original Android Development] mohammedtabish:
i already got the ans from masterawesome and thats why he changed the code from this will void your warranty to this may void your warranty

and btw thanks for sharing
[OnePlus X Original Android Development] dtosun:
What does it mean? Will we have CM13 soon?
[OnePlus X Original Android Development] sgroimax:
V75 is ok
[OnePlus X Original Android Development] CertifiedBlyndGuy:
I don't think we'll see it for at least a month. 12.1 needs to get stable first
[OnePlus X Original Android Development] gladiac:
Hi [MENTION=5321417]MasterAwesome[/MENTION],

I made a commit which adds DriveDroid support to the onyx msm8974 kernel. This patch is necessary for the DriveDroid app to function properly. Other cyanogenmod kernels also have support for it so I thought onyx deserves it too :). Here is the change ready for you to be fetched. I could not really test it so I hope it just works fine.

Have a nice weekend,

glad
[OnePlus X Original Android Development] jonrodz:
What opx version are you running?

---------- Post added at 07:31 PM ---------- Previous post was at 07:30 PM ----------

Are you on opx us version?

---------- Post added at 07:31 PM ---------- Previous post was at 07:31 PM ----------

What version are you on? E1001, E1003, E1005?
[OnePlus X Original Android Development] flafla:
Hello, does "no working speaker mic" mean voice calls dont work yet?
[OnePlus X Original Android Development] Sundar1995:
Yes tested on other phone only. I was using another phone to call to my phone and hear the person voice using my phone clearly.

No echo... I bought it via Amazon.in India and my carriers are Airtel and Vodafone India

---------- Post added at 08:19 AM ---------- Previous post was at 08:18 AM ----------

Voice on calls isn't working...you can only hear the other person speaking but can't reply via microphone
[OnePlus X Original Android Development] sgroimax:
Yes the mic during a phone call doesn't works. But it doesn't mean that u can't get a call. It meas that the call can be done only via normal behavior. So u cannot put your phone on a table and speak with other on live voice. So also Google voice doesn't work because of the mic issue.
[OnePlus X Original Android Development] RinoFxx:
V9.0 working very good as I told yesterday but from the first release I have the 100% bug state yet! How can I solve that? It's very annoying reboot phone every time to solve it. This is the only bug I encountered, the speaker mic doesn't important for me!

Inviato dal mio ONE E1003 utilizzando Tapatalk
[OnePlus X Original Android Development] Firefly1337:
I tested this build (V9.0) for two days now and I'm going back to stock. Thank you MasterAwesome for your work, but this build is simply not stable yet. Too many little things do not work and they add up.

In Germany we have a saying "Kleinvieh macht auch Mist", which apparently translates to "Many a little makes a mickle".

Bugs I encountered:

- Battery 100% bug after charging: I rebooted 2 times and it still shows 100%. Strangely I only had that this morning, yesterday was fine. This irregular behavior makes this bug even worse, in my opinion.

- Gestures menu in settings doesn't visually remember what I enabled (functions work, they just forget their state). If I "re-enable" them they get inverted.

- Gesture menu in settings is not themeable (no matter what theme I use, it's always white per default)

- I didn't check for echo, but obviously this is still a bug (I applied the flashable zip "fix")

- "Speaker mic" not working, as stated several times already

- Other mic related stuff (e.g. "Ok Google") not working

- Quickly switching the tri-state-key seems to confuse the system. It does not know where it is after a while.

- Something else I can't remember right now

- ...

Device: E1003 with o2 Germany

Overall stability was good, I really liked it. If the above bugs are fixed, I'll definitely come back using it.

I have the feeling this ROM will be good, but it will take some time to make it truly stable.
[OnePlus X Original Android Development] taaeem:
This post is no offense against OP but I think many of the little bugs come from the device tree being based on the bacon one and not written from scratch.
[OnePlus X Original Android Development] gladiac:
Yes, this is what happens when vendors don't release their device-trees. You take the next best thing that you have - in this case the bacon device-tree - and hope for the best. Bugs like the EAP-SIM bug are a direct consequence of that. However, I think this ROM is in pretty good shape already. Sure, some things are still broken but there are talented people out there working on them. Compare this device to, say like, the Galaxy S6 where it will still take months until CM will kinda work on it...
[OnePlus X Original Android Development] Bkam13:
I've seen that they will release source code and other stuff soon, on a forum post, where OP admin were talking about custom roms. Maybe a good new for us !
[OnePlus X Original Android Development] ravinder0003:
Exact the same bugs i have... Great
[OnePlus X Original Android Development] sydeu:
The gesture menu is themeable, it's your themes that isn't doing it. Try blacked out by chumps team, it makes the gesture menu pitch black like I want it.

Otherwise you are correct.

---------- Post added at 04:09 PM ---------- Previous post was at 04:04 PM ----------

@MasterAwesome BankID and swish still crashes when you try to start them. Works on rooted devices and on OxygenOS so that's not the problem. Here is a thread and logcats for the problem:

http://xdaforums.com/oneplus-x/help/bankid-swish-dont-cm-12-1-t3269629/page2#post64621279

Would be really appreciated if you could have a look at this because these apps are really important for everyone in Scandinavia.
[OnePlus X Original Android Development] Firefly1337:
Tried that one, too. Unfortunately not working for me (I did a reboot, too).

Plus it isn't translated. I selected german but the menu was english, so maybe that has something to do with it.

But to be honest, I don't really care about that. Other bugs are more important right now.
[OnePlus X Original Android Development] sydeu:
I see, that's weird. It's working perfectly for me both on 9.0s and on 2.0s which I just updated from (I always clean flash)
[OnePlus X Original Android Development] sgroimax:
I don't agree with you. Tri state keys work well, no echoes found, the themable things are very insufficient goals for me, gestures work fine. So I respect your decision but at this time this ROM can be used how daily driver. Thanks [MENTION=5321417]MasterAwesome[/MENTION]
[OnePlus X Original Android Development] ravinder0003:
Tri state keys behave strange...

Just try them sliding up and down 4-5 times...

Then it will start forgetting options selected...
[OnePlus X Original Android Development] YumeMichi:
the same to sydeu. tri state keys works abnormally on my phone, it often forgets where is it. such as I switch the key to top, but it's not mute, it's ruleless...

---------- Post added at 04:50 PM ---------- Previous post was at 04:36 PM ----------

Everytime I flashed your rom, the Music app could not recognize my music files. I had to delete all of my music from sdcard and internal storage, and copied them to sdcard again. Gallery also. Other mobile apps were not recognize music and picture. I can only see them in file explorer

and everytime I flashed this your rom, all of files in internal storage before flashing were not recognized in computer side, such as I took a screenshot named "1.png", then I flash your rom. after that I connect my phone to computer. the "1.png" does not show in explorer.

If I took another screenshot, it would be recognized.
[OnePlus X Original Android Development] widewing:
is OK Google issue really related to the mic?

After the mic fix, the OK Google still not work, and the Google voice search too. Since every other mic related apps are working pretty well, I suspect that this issue is not related to mic.

In Logcat, when using Google voice search, the following log is repeated a huge amount

...
E/ActivityThread( 2140): Failed to find provider info for com.google.android.apps.gsa.testing.ui.audio.recorded
E/ActivityThread( 2140): Failed to find provider info for com.google.android.apps.gsa.testing.ui.audio.recorded
E/ActivityThread( 2140): Failed to find provider info for com.google.android.apps.gsa.testing.ui.audio.recorded
...
I/MicrophoneInputStream( 2140): mic_close com.google.android.apps.gsa.extradex.emulatormicrophone.b@1652da87
E/ActivityThread( 2140): Failed to find provider info for com.google.android.apps.gsa.testing.ui.audio.recorded
...

I decompiled the Google app, and searched for "com.google.android.apps.gsa.testing.ui.audio.recorded" and "com.google.android.apps.gsa.extradex.emulatormicrophone" but no luck.

Then I looked into the /data/data/com.google.android.googlequicksearchbox and found that the class "com.google.android.apps.gsa.extradex.emulatormicrophone.b" is actually reside in /data/data/com.google.android.googlequicksearchbox/files/extradex_jars/XGsF7Ec20jaWmEKIhWg3g2Q/verified/emulatormicrophone/emulatormicrophone-0.jar

Apparently this class file is downloaded and imported at runtime.

By decompiling this file, we can see class b is :

package com.google.android.apps.gsa.extradex.emulatormicrophone;

import android.content.Context;
import android.media.AudioRecord;
import android.net.Uri;
import com.google.android.apps.gsa.speech.audio.aa;

public class b
extends aa
{
private static final Uri aDr = Uri.parse("content://com.google.android.apps.gsa.testing.ui.audio.recorded/emulated_mic_audio");
private final int aDs;
private final Context gb;

public b(int paramInt, Context paramContext)
{
super(paramInt, 128000, 16, false, null, false);
this.aDs = paramInt;
this.gb = paramContext;
}

protected AudioRecord yZ()
{
return new c(this, this.aDs);
}
}

The problem is "com.google.android.apps.gsa.testing.ui.audio.recorded" is no where in our phone.

Since there is a "testing" in this package name, I suspect this file is not google intend to provide, but maybe a trigger parameter or something makes google think we are in "testing mode" or something?

So to solve this issue, I think we can try two ways: 1) find out the parameter to get google app download the right jar file, 2) Looking into other phones which the OK Google is working and port that same file to see if works
[OnePlus X Original Android Development] sydeu:
[MENTION=5321417]MasterAwesome[/MENTION] I can confirm echo on clean flash 9.0s. European E1003.
[OnePlus X Original Android Development] blackdroid52@gmail.com:
Please update change log here..
[OnePlus X Original Android Development] CertifiedBlyndGuy:
I'll try finding and testing the package. I'll get back with results.
[OnePlus X Original Android Development] theSander:
Has anyone else got problems with mobile data? My phone seems unable to connect to it very frequently. Sometimes it's OK, and then a few mintes later it's gone. I'm on 8.0s.

EDIT: Belgium, Mobile Vikings
[OnePlus X Original Android Development] CertifiedBlyndGuy:
Somewhat unfortunate news. The Nexus 6 was having issues in CM13 that surrounded that file. I found this:

http://forum.cyanogenmod.org/topic/118914-cm13-missing-global-ok-google-detection/

The conclusion is that it's a big with CM. When app data is restored from another device it should work fine. The question is, who wants to factory resrt a Nexus or something and zip their data folder? :)
[OnePlus X Original Android Development] MasterAwesome:
You guessed right, it triggers the test. No that's not how it works though. Audio HAL doesn't know what the mic is. All it does it change some ctl values and the kernel takes care of the rest. But here's the problem the HAL doesn't know which the mic is. If you look at mixer_paths.xml there are multiple defs for mic, endfire for example is what our device uses. So HAL doesn't use correct devices. Either modify the HAL(what oneplus did) or modify the mixer paths or modify audio_platform_info.xml(preferable). The way to get acdb ID is basically objdump the stock library and look at the .data section. I need to look into it. I haven't had time, I've just been trying to hack my way through the actual problem. It's a pretty simple fix though.
[OnePlus X Original Android Development] Sundar1995:
The ok Google voice detection problem is not there in cyanogenmod 13 by [MENTION=5426059]ashwin007[/MENTION]. Strange
[OnePlus X Original Android Development] CertifiedBlyndGuy:
I could do it real quick. It wouldn't take but an hour. I'll upload the zip to drive.
[OnePlus X Original Android Development] MasterAwesome:
Knock yourself out. Just upload the zip here, let users test it, if it works good, create a pull request.
[OnePlus X Original Android Development] CertifiedBlyndGuy:
Here's the libraries. I'm not really familiar with objdump at this point.

https://drive.google.com/file/d/0B_uXgn68zsudSnZCTHk4eWx0Y2c/view?usp=docslist_api

I figured downloading 30mb is better than downloading a gigabyte and then flashing to extract it.
[OnePlus X Original Android Development] MasterAwesome:
Just do this

arm-linux-androideabi-objdump audio.primary.msm8974.so -D -j .data | grep -n '00000067' | head -1 | cut -d':' -f1

this will tell you the starting line number. the acdb_table is 304 bytes long == 76 lines of code from there. you should be able to figure it out after that. I'll probably do this after a while, got my exams coming up.
[OnePlus X Original Android Development] jonrodz:
I know this question doesnt have to do with the development of the rom, but has someone done an antutu test? And I know antutu score aren't always reliable, but i just want to know...
[OnePlus X Original Android Development] sydeu:
i did, got 50k i think.
[OnePlus X Original Android Development] MasterAwesome:
Screenshot section.
[OnePlus X Original Android Development] XqepX:
So why are you asking if you know it's wrong?

Anyways it's from 45 000 to 50 000, depending on clock speeds, governor and so on
[OnePlus X Original Android Development] CertifiedBlyndGuy:
I'm working on it. I should be able to fix this by tonight.

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

Just under 50k. It runs amazingly fast in comparison to stock. I do recommend replacing AufioFX with Viper4Android though as t adds more functionality
[OnePlus X Original Android Development] jonrodz:
Cause if i ask this on the antutu scores thread in oneplus x general, im not going to get an answer as soon as on this thread. Thanks anyway for answering my wrong question. ;) Sorry!
[OnePlus X Original Android Development] CertifiedBlyndGuy:
So running:

./arm-linux-androideabi-objdump audio.primary.msm8974.so -D |grep acdb

Returned:

0000b5d8 <platform_set_snd_device_acdb_id>:

b5ec:	8a000005	bhi	b608 <platform_set_snd_device_acdb_id+0x30>

b5f0:	e59f003c	ldr	r0, [pc, #60]	; b634 <platform_set_snd_device_acdb_id+0x5c>

b608:	e59fe028	ldr	lr, [pc, #40]	; b638 <platform_set_snd_device_acdb_id+0x60>

b60c:	e59f1028	ldr	r1, [pc, #40]	; b63c <platform_set_snd_device_acdb_id+0x64>

b610:	e59f3028	ldr	r3, [pc, #40]	; b640 <platform_set_snd_device_acdb_id+0x68>

b630:	eafffff2	b	b600 <platform_set_snd_device_acdb_id+0x28>

148a0:	ebffdb4c	bl	b5d8 <platform_set_snd_device_acdb_id>

./arm-linux-androideabi-objdump: 0001d50c <acdb_loader_get_calibration>:

What can I do from here?
[OnePlus X Original Android Development] MasterAwesome:
That's why you don't grep acdb. If you readelf -s audio... You'll see symbols have been stripped. You'll have to search the hex of a value. Hence the 00000067 in my other post
[OnePlus X Original Android Development] CertifiedBlyndGuy:
Oh okay. The starting numeral of the hex is 97.

readelf -s audio.primary.msm8974.so |grep 97

Returns:

97: 00000000 0 FUNC GLOBAL DEFAULT UND pcm_close

166: 0000973c 52 FUNC GLOBAL DEFAULT 8 pcm_ioctl

171: 00009770 400 FUNC GLOBAL DEFAULT 8 stop_call

177: 00009974 40 FUNC GLOBAL DEFAULT 8 voice_get_active_session_

197: 00000000 0 FUNC GLOBAL DEFAULT UND str_parms_del
[OnePlus X Original Android Development] primemonitor:
Just noticed this on 9.0s : Frame rate on any of the 16:9 resolutions in the Camera app is very slow. All 4:3 resolutions are fine, but 16:9 is very very slow. I'd clean flashed the rom, and also tried Google Camera. Same thing with both the Camera apps.
[OnePlus X Original Android Development] MasterAwesome:
Umm, you don't need symbols you need data. Use the command 3 posts ago, the one with objdump

arm-linux-androideabi-objdump audio.primary.msm8974.so -D -j .data | grep -n '00000067' | head -1 | cut -d':' -f1
[OnePlus X Original Android Development] CertifiedBlyndGuy:
I'm so sorry man. That just returns '97' for whatever reason. I thought it correlated with a hex or something.
[OnePlus X Original Android Development] MasterAwesome:
That's the line number. arm-linux-androideabi-objdump audio.primary.msm8974.so -D -j .data | grep -n '00000067' -C 76 | tail -76

That should display the values.
[OnePlus X Original Android Development] MasterAwesome:
The line numbers should start from 97 what you got as an output previously. grep -A 43 Chuck the pipe to tail.

arm-linux-androideabi-objdump audio.primary.msm8974.so -D -j .data | grep -n '00000067' -A 43
[OnePlus X Original Android Development] MasterAwesome:
Okay so I had a bit of time so I decided to look into it. I found out that something is not calling the HAL properly.

when using Google Now it logs this.

This is how it should look like

D/audio_hw_primary( 284): start_input_stream: enter: stream(0xb586e7e0)usecase(7: audio-record)
E/audio_hw_primary( 284): select_devices : usecase->type=1
D/audio_hw_primary( 284): select_devices: out_snd_device(0: ) in_snd_device(47: headset-mic)
D/audio_hw_primary( 284): select_devices: done
I/msm8974_platform( 283): platform_send_audio_calibration: sending audio calibration for snd_device(31) acdb_id(41)
D/ACDB-LOADER( 283): ACDB -> send_audio_cal, acdb_id = 41, path = 1 #CALLS MIC here

this is what it looks like.

D/audio_hw_primary( 284): start_output_stream: enter: usecase(1: low-latency-playback) devices(0x4)
E/audio_hw_primary( 284): select_devices : usecase->type=0 #ERROR HERE should call type=1 which is PCM_CAPTURE
D/audio_hw_primary( 284): select_devices: out_snd_device(4: headphones) in_snd_device(0: ) #YOU CAN SEE in_snd_device is empty.
D/audio_hw_primary( 284): select_devices: done
I/msm8974_platform( 283): platform_send_audio_calibration: sending audio calibration for snd_device(2) acdb_id(15)
D/ACDB-LOADER( 283): ACDB -> send_audio_cal, acdb_id = 15, path = 0 #CALLS SPEAKER HERE

So basically the problem is because the APP never calls for a audio capture. The question is why doesn't it call for audio capture when other applications can do it. Similar thing happened while using stock libs too which means it's a problem with the operating system handling the calls(IMPOSSIBLE since it works on other phones + other apps works fine). which further leads to google now being faulty. Speaker mic works now though, so i'll upload a build soon.
[OnePlus X Original Android Development] parasthakur37:
[MENTION=5321417]MasterAwesome[/MENTION] please can you have the next build built with sabermod or linaro?
[OnePlus X Original Android Development] Drakorcarnis0:
Thank you for this awesome work it runs fine and I've great battery life. There is however one thing that messes me up: controlling music by long pressing volume buttons doesn't work.

EDIT: It was xposed that messed up this feature. Just uninstalled xposed and it works back. Maybe there is a way two make both work together.
[OnePlus X Original Android Development] dtosun:
Hi @MasterAwesome,

Thank you for your good support and development. Google now is working good in CM13. Can you develop for CM13 and solve bugs for stable.
[OnePlus X Original Android Development] CertifiedBlyndGuy:
Swell. Literally just woke up and started tracing those values, but it looks like you managed to obtain them. Really sorry I couldn't get them. Thanks for the great work. I can't name another mod that would go through all of this without the source for a device being released

---------- Post added at 12:28 PM ---------- Previous post was at 12:25 PM ----------

I believe he's said it before, but 12.1 needs work before 13 even gets considered. It's not like these things are made overnight lol. I'd actually prefer he prepared for his exams. That's more important in the long run
[OnePlus X Original Android Development] saurabh40629:
Yeah, he should. btw let me know when exams are over. Party is on me.
[OnePlus X Original Android Development] MasterAwesome:
Haha, Exams start tomorrow. Coffee and no sleep it is. #justEngineeringThings.
[OnePlus X Original Android Development] sgroimax:
Come on with exams guys. Real life is more important than development. Happy exams. I am from your side
[OnePlus X Original Android Development] saurabh40629:
Man, I miss those days. Now i just code in java with lots of cofee . You guys are doing it for hobby and I do it now for living . I know you guys are smart, but if you ever need any help, do pm me.
[OnePlus X Original Android Development] angad010594:
Flashed d ROM and its stable too.. A problem faced by me is hardware buttons.. That I can't use I have to enable on screen keys that I don't like.. Hardware keys r not responding as they should..
[OnePlus X Original Android Development] Drakorcarnis0:
They work perfectly fine for mine. Ya can modify their behaviour in settings/buttons
[OnePlus X Original Android Development] angad010594:
Thanx buddy it helps...
[OnePlus X Original Android Development] vanessaem:
Thread cleaned and the off topic bickering has been removed. Please stay on topic and keep peace on the thread.

Regards