yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Alpha] Olangu:
I've noticed that when answering calls the mic takes a long time to become activated. People usually can't hear my first "hello". Don't know if it's just generally slow to answer the call or if its just the mic.
[Samsung Galaxy Alpha] nuno.f.ferreira:
+1

This is probably related with the timer in place to reload firmware. Modpunk is being conservative to make sure it works but that means we start hearing with a delay.

I guess the better fix would be to use inotify and change to an event based strategy but I don't think we are going to have more patches for cm12.1...
[Samsung Galaxy Alpha] miszko77:
Hi modpunk,

could you provide me fix for headphones via bt? I cant just use your rom because calling on it is not working for me at all. I am quite happy with rremix rom but it has bugged playback via bt. I will be very grateful.
[Samsung Galaxy Alpha] Blubberor:
Check first 3 posts and provide information...
[Samsung Galaxy Alpha] hDusan:
The next release which will be cm13 or update cm12.1 yet ? :)

Tapatalk-kal küldve az én SM-G850F-el
[Samsung Galaxy Alpha] Ashareth:
He is working on CM13 mostly, but said it will take a couple weeks to get a booting/"working" CM13 version.

Recently he worked to fix a few bugs on CM12.1 while waiting for a few things to be done upstream in CM13, so i guess he'll do that till there is a CM13 tree workable enough for him to test it on his phone.
[Samsung Galaxy Alpha] MisterEcks:
Hi All,

Does anyone else experience issues when using BT connections? Specifically judders and interruptions when using spotify? It is significantly worse when Wi-Fi is enabled. Turning off wifi seems to help a lot.

I am wondering if it is an issue with CM12.1 as I have 2 devices (Note II and Alpha) and both have the same issues. Using the same BT speakers and heaphones on non-CM12 devices works fine so i don't think its anything to do with the BT devices themselves.

Any advice?
[Samsung Galaxy Alpha] Blubberor:
For ne reflashing of Viper 4audio helped.

Best and good luck
[Samsung Galaxy Alpha] scoddster:
Would you have a URL for the package you've flashed?

Thank you
[Samsung Galaxy Alpha] Blubberor:
Here you go.

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

Good luck!
[Samsung Galaxy Alpha] scoddster:
Thank you, flashed it and it got a bit better actually. Still have hiccups but far less than before. Interestingly, although viper driver is loaded, the equalizer and none of the effects is working. (still got better BT audio with the Sony SBH80 though).

Are you "hiccup free"?

Is the equalizer working for you?
[Samsung Galaxy Alpha] Blubberor:
Not100% status still abnormal in the Viper status.
[Samsung Galaxy Alpha] MisterEcks:
Sadly this has not helped.

I suspect this is an issue with the the Bluetooth driver / hal as interference from WiFi is significant.

Perhaps under cm13 there will be an improved experience?
[Samsung Galaxy Alpha] Olangu:
Yes, the mic really likes to pick upp sound from the earpiece. Lowering the volume of incoming sound usually helps. The mic also gives poor sound quality in noisy surroundings.
[Samsung Galaxy Alpha] omarmonajed:
I suggest you download oszan rom as a daily stable driver if you like touchwiz
[Samsung Galaxy Alpha] hDusan:
How to use hearth reate services or witch app work this ?
[Samsung Galaxy Alpha] modpunk:
The fingerprint sensor doesn't work so the heart beat sensor doesn't work either. Feel free to help with a fingerprint HAL implementation for vfs61xx ...
[Samsung Galaxy Alpha] tileeq:
So im guessing theres no hope for fingerprint in marshamallow either?

Sent from my SM-G850F
[Samsung Galaxy Alpha] hDusan:
The Marshmallow have native support fingerprint sensor, therefore will be work on android 6.0

And modpunk I deal developmenting...

How to made "one" or work incule ?
[Samsung Galaxy Alpha] Ashareth:
Not totally true.

As he explained before, the *technology* for Fingerprint Sensor is in Android M... the drivers for specific Fingerprint Sensors depends on the hardware manufacturers. And since Galaxy Alpha didn't get Android 5.1 already, it won't get Android M (or it's weird) from Samsung, so there will probably be no driver for the Fingerprint Scanner.

So unless a phone with the same sensor get Android M and some dev can backport the driver to our phone roms, there won't be support for fingerprint sensor/scanner either with Android M for the Alpha.
[Samsung Galaxy Alpha] :
LIES. It will get 6.
[Samsung Galaxy Alpha] Ashareth:
I would *love* an official announcement about that because it would probably means easier porting of CM13 to our devices. xD
[Samsung Galaxy Alpha] omarmonajed:
Calm down dude.

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

Oh wait, it says universal KID
[Samsung Galaxy Alpha] Blubberor:
Back to the topic of the thread..

Music hick-ups wheb BT streaming is memory dependent.

I use "es task killer" as additional memory killer. After freeing the memory while having BT streaming hick-ups brings normal playback back.

Best,

blubberor
[Samsung Galaxy Alpha] modpunk:
I have some changes in the memory area in the kernel for 13.0. I hope they will be gone then. However I don't have much time to work on CM right now.
[Samsung Galaxy Alpha] Beukhof1:
Can someone old create a new build of this with the last cm commits
[Samsung Galaxy Alpha] Ashareth:
Doubt it will happen since the only few devs working on Alpha (mostly modpunk, Raymann, Sunset and Kyasu from what i know) have moved on CM13 port/work.

You would have to do that yourself or wait mostly.
[Samsung Galaxy Alpha] sphazer:
Modpunk are you going to release a first version of the rom anytime soon...sorry for the eta but sunset released rr 5.6.0 and i want to see which one behaves better
[Samsung Galaxy Alpha] Blubberor:
Just wanted to mention with latest xef modem and clean install everything including BT streaming works.

Looking forward to marshmellow.
[Samsung Galaxy Alpha] omarmonajed:
Cool
[Samsung Galaxy Alpha] modpunk:
Then the ROM you are using has SELinux disabled, else gpsd wouldn't work and probably the Camera too.

The ROM is not in a fully useable state for the average user yet.
[Samsung Galaxy Alpha] Blubberor:
At least I did not find anything not working. Selinux is unchanged to "strikt".

Only thing i changed CPU govenor to userspace - somehow since then the phone doesnt freeze anymore(i suspect CPU throteling being the cause as this occurs with stock as well).
[Samsung Galaxy Alpha] modpunk:
LD_SHIM_LIBS doesn't work any more, SELinux is preventing access to the variable. So we do not load shim libs for gpsd and camera blobs. I've hacked it for the camera blob but it doesn't work for gpsd, you have to manually start it. Also bluetooth will not work on semco devices with the latest version. I've just fixed that ...
[Samsung Galaxy Alpha] Blubberor:
just to clarify.

using Baseband: G850FXXU1COJ5 (coming from this firmware: https://samsung-firmware.org/de/download/Galaxy-Alpha/z9o0/XEF/G850FXXU2COK1/G850FOXACOJ2/)

Telefon Samsung Galaxy Alpha

Modell SM-G850F
PDA-Version G850FXXU2COK1
CSC-Version G850FOXACOJ2
PHONE-Version G850FXXU1COJ5
Region XEF
Land France
Erstellungsdatum 06.11.2015
Änderungsliste 6200756
Betriebssystem Lollipop
Version Betriebssystem 5.0.2

as said bt phone and music works, as well as navigation...

If this should not I can provide logcats in case this helps.

But not sure if I got you correct before.
[Samsung Galaxy Alpha] kamillopl:
I restore my phone and phone dead. I restore from phone not twrp. I have samsung logo and later twrp logo - not CM logo. This is all. Download mode working but when i put twrp on my phone by Odin the problem not disappear. I can't enter in twrp.
[Samsung Galaxy Alpha] pal.sch84:
I know, its a bit late, but maybe it helps some other. In such a case you can download the stock firmware (using SamFirm) and flash that with Odin in download mode. This should normally fix all. After that you can flash the custom roms again.
[Samsung Galaxy Alpha] modpunk:
This is strange, it can start the modem daemon.

audit(1441264651.340:440): item=0 name="/system/bin/cbd" inode=40740 dev=103:0a mode=0100755 ouid=0 ogid=2000 rdev=00:00 obj=u:object_r:system_file:s0
audit(1441264656.355:441): avc: denied { entrypoint } for pid=8715 comm="init" path="/system/bin/gpsd" dev="mmcblk0p18" ino=40778 scontext=u:r:gpsd:s0 tcontext=u:object_r:system_file:s0 tclass=file

But this looks wrong cbd is set to cpboot-daemon_exec and should be allowed to access it as entrypoint:

domain_trans(init, cpboot-daemon_exec, cpboot-daemon)

This line allows it ...

It looks like it didn't label your system correctly.
[Samsung Galaxy Alpha] modpunk:
I found the problem. The updater in the TWRP sources don't support version 3 transfer lists -> https://android-review.googlesource.com/#/c/140510/

TWRP is missing https://android-review.googlesource.com/#/c/140448/ in the updater, so it can write the system.img to the block device. I will create a beta2 soon ...
[Samsung Galaxy Alpha] modpunk:
I've released beta2 ...
[Samsung Galaxy Alpha] Blubberor:
So

Music over Bluetooth works

Bt phone not working

Voice quality of regular calls with hall. Only narrow band?

Beside this no bugs found.

Cheers,

blubberor
[Samsung Galaxy Alpha] modpunk:
I try to get a bluetooth headset and revist the config and audio hal.

Do you mean you have an echo during voice calls? I have clear voice ....
[Samsung Galaxy Alpha] Blubberor:
Yes, called my girlfriend and had the same call quality as in the initial cm12.1 release from kyasu.(exactly same pattern and quality)

For bt i guess its "simple" routing issues.

Thanks and best,

blubberor
[Samsung Galaxy Alpha] modpunk:
Is there someone with a bluetooth headset who knows how to use adb to push files to the system partion?

I think I've fixed it. I do not find my old bluetooth headset to test it.
[Samsung Galaxy Alpha] miszko77:
Yes I can confirm that voice quality is robotic and echo exist.
[Samsung Galaxy Alpha] Blubberor:
Me but only next week. But copying files with root would be even easier ;)
[Samsung Galaxy Alpha] nuno.f.ferreira:
Me too. Currently using kyasu's ROM here. I need to wipe it clean first, right?

Please let me know what you need me to do and I'll probably be able to do it today or tomorrow morning.
[Samsung Galaxy Alpha] Mokson:
What about searching network operators returns an error and empty list.

Does this bug actual in current build?
[Samsung Galaxy Alpha] miszko77:
yes
[Samsung Galaxy Alpha] modpunk:
First allow writing to system:

mount -o remount,rw /system

Get the files from:

https://xor.cryptomilk.org/android/bt_sco_test/

The shared library needs to go to /system/lib/hw and the xml file to /system/etc.

You can simply do 'killall -TERM mediaserver' with a root shell and it will be reloaded ...
[Samsung Galaxy Alpha] nuno.f.ferreira:
Congrats, bluetooth headset works fine

Bluetooth in the car doesn't though and this is the one I really want :)

The bug "INCALL: The device needs 12-20 seconds to wake the screen on an incoming call" doesn't exist for me

Confirm camera is buggy.

In phone call the other side ears me well but I hear a somewhat "robotic" sound, but if I'm using bluetooth headset I hear fine. No echos in anycase.

Waiting for more versions to test :)

---------- Post added at 07:16 PM ---------- Previous post was at 06:30 PM ----------

One more thing, at first it seemed that the device now becomes hotter. This also happened with kyasu's ROM after he switched to 5130 kernel and libs.

Having said that I rebooted and it didn't happen again.

Other issue I have is that now I have no LTE.

Wish I could stick with this ROM but perhaps I need to go back for a while...

---------- Post added at 07:33 PM ---------- Previous post was at 07:16 PM ----------

Sorry, please ignore this one. It was just the default config that was off.
[Samsung Galaxy Alpha] modpunk:
Great, I didn't look into bluetooth carkit support yet. I'm not available next week but will try to fix it the week after ...

The "robotic" voice is the default android noise suppression I think ... I need to check if we turn it off for now or if we get it working with 5.1.1
[Samsung Galaxy Alpha] modpunk:
Didn't it work at all, did audio output not work or did the mic not work?
[Samsung Galaxy Alpha] nuno.f.ferreira:
Pairing worked but no audio at all, in or out. From the phone's perspective symbol/icon presented is the expected one but from the car's side pairing works but immediately after it is gone. No audio, not even ringtone.
[Samsung Galaxy Alpha] Mokson:
Anyone wants to try to fix Operators Search error?

Looks like search result returns 6 columns and OS expects only 4

http://review.cyanogenmod.org/#/c/85732/
[Samsung Galaxy Alpha] modpunk:
They are correctly set, see:

https://git.cryptomilk.org/projects...internal/telephony/SlteRIL.java?h=cm-12.1#n58
[Samsung Galaxy Alpha] cooldoc007:
a similar issue which was solved in 910c.. not sure if its the same here.. can check here.. http://xdaforums.com/showpost.php?p=61799656&postcount=781

its about the robotic voice
[Samsung Galaxy Alpha] modpunk:
BETA3 is out!

Bluetooth headsets are working. If you have a carkit, please connect your phone to a PC and run 'adb logcat -c'. Go to your car and test carkit bluetooth support. If it doesn't work, get the log with 'adb logcat' and post it here.
[Samsung Galaxy Alpha] nuno.f.ferreira:
Unfortunately I haven't got good news but first of all let me inform you that I installed this ROM on top of kyasu's ROM, only wiped the cache.

Ok, so what were the results.

Standard voice calls are placed but on my side I don't hear ringing nor anything else when the other side answers they only hear low volume noise. Log attached for this is std-call.log

Then I went to my car (BMW ConnectedDrive) and bt pairing didn't work. bt-pairing.log attached. Please note that bt worked before for your ROM. Looks like problem with SELinux.

I have to go back to my backup. Please let me know if you need anything else tested.

And thanks for all your hard work!
[Samsung Galaxy Alpha] Mokson:
could you fix Network Operators Search error?
[Samsung Galaxy Alpha] modpunk:
Phonecalls have great quality for me and others hear me very well. I do not see something which went wrong on your phone in this case. WB support is turned on ...

The default bluetooth module crashes. To find out what is going on I need a carkit for testing ...
[Samsung Galaxy Alpha] modpunk:
I can look into it next week ...
[Samsung Galaxy Alpha] nuno.f.ferreira:
Well, I would say that there is something wrong with this third version. Except for the robotic voice beta2 was just fine for standard voice calls. BT pairing also worked although at the time I tested it in a different car that I don't have right now.

I just tried a full wipe and the behaviour is the same.

From the bt-pairing.log

Guess this is not bt related...

"StrictMode policy violation; ~duration=103 ms: android.os.StrictMode$StrictModeDiskReadViolation: policy=31 violation=2"

Isn't this a problem?

"D/BluetoothManagerService( 2812): Message: 20

D/BluetoothManagerService( 2812): Added callback: android.bluetooth.IBluetoothManagerCallback$Stub$Proxy@3b6477a:true

W/ContextImpl( 6896): Calling a method in the system process without a qualified user: android.app.ContextImpl.startService:1721 android.content.ContextWrapper.startService:522 android.content.ContextWrapper.startService:522 com.android.settings.bluetooth.DockEventReceiver.beginStartingService:134 com.android.settings.bluetooth.DockEventReceiver.onReceive:115

D/DockEventReceiver( 6896): finishStartingService: stopping service

E/BTEventHandler( 6960): A4WP is not supported"
[Samsung Galaxy Alpha] modpunk:
After beta 2 I just fixed bluetooth. I didn't change normal voice calls. Did you flash the modem from a LL stock ROM?

Yes, this could be the issue with bluetooth, however I do not know what it means yet ...
[Samsung Galaxy Alpha] nuno.f.ferreira:
Yes I did. Also I'm currently back to using kyasu's ROM and normal voice calls work again.
[Samsung Galaxy Alpha] ke_be:
Good jab with beta3 :) But I have 2 questions. When you plan to fix camera? Now it crash every 1-3 photo and start very slow. Also after camera crash there is battery drain problem (1% for ~5min).

And what about low sound record?
[Samsung Galaxy Alpha] modpunk:
I dunno maybe soon, maybe not. It is a big debugging effort.
[Samsung Galaxy Alpha] modpunk:
I would say it is the big WARNING you see and the segfault in the first place ..
[Samsung Galaxy Alpha] modpunk:
From which ROM? I use the France 5.0.2 release for development.
[Samsung Galaxy Alpha] nuno.f.ferreira:
At the time I believe I used this one http://installandroidrom.blogspot.pt/2015/05/install-g850fxxu2cod4-xxu2cod4-on.html

The baseband I'm using is G850FXXU1COC1.

I don't mind changing if that will enable me ti start using your ROM now, camera is not blocker for me. So let me know if you prefer to support this modem and I'll stick with it and test your next betas. If you don't want to add extra support I would appreciate if you could send a link so that I can flash the same modem you have... if you have a flashable modem.zip even better :)
[Samsung Galaxy Alpha] modpunk:
The blobs of the CM ROM come from: http://www.sammobile.com/firmwares/download/46564/G850FXXU2COD4_G850FOXACOD4_XEF/

I also use the modem firmeware and bootloader from this ROM
[Samsung Galaxy Alpha] nuno.f.ferreira:
Thanks, will download it now so I haven't seen it yet but I want to ask. Can I install just the BL and modem firmware using Odin or must I tick AP and go through the full process with the stock ROM?
[Samsung Galaxy Alpha] modpunk:
I don't know. I use heimdall on Linux and just flashed the sboot.img and modem.bin.
[Samsung Galaxy Alpha] nuno.f.ferreira:
Great, I'm also a Linux user but normally don't use Heimdall because of the firmware.xml that is not supported by OEMs but I'm just fine with using the CLI tool. So just to check, is this what I should do?

heimdall flash --primary-boot sboot.img --modem modem.bin --verbose
[Samsung Galaxy Alpha] modpunk:
You need to get the pit file first ...
[Samsung Galaxy Alpha] nuno.f.ferreira:
Sorry, to bother your with this but is this known to you (protocol errors bellow)?

$ sudo heimdall print-pit --no-reboot --verbose

Heimdall v1.4.1

Copyright (c) 2010-2014 Benjamin Dobell, Glass Echidna

http://www.glassechidna.com.au/

This software is provided free of charge. Copying and redistribution is

encouraged.

If you appreciate this software and you would like to support future

development please consider donating:

http://www.glassechidna.com.au/donate/

Initialising connection...

Detecting device...

Manufacturer: "SAMSUNG"

Product: "Gadget Serial"

length: 18

device class: 2

S/N: 0

VID:PID: 04E8:685D

bcdDevice: 021B

iMan:iProd:iSer: 1:2:0

nb confs: 1

interface[0].altsetting[0]: num endpoints = 1

Class.SubClass.Protocol: 02.02.01

endpoint[0].address: 83

max packet size: 0010

polling interval: 09

interface[1].altsetting[0]: num endpoints = 2

Class.SubClass.Protocol: 0A.00.00

endpoint[0].address: 81

max packet size: 0200

polling interval: 00

endpoint[1].address: 02

max packet size: 0200

polling interval: 00

Claiming interface...

Setting up interface...

Initialising protocol...

ERROR: Failed to receive handshake response. Result: -7

ERROR: Protocol initialisation failed!

Releasing device interface...
[Samsung Galaxy Alpha] modpunk:
The no-reboot option never worked for me and gave me this error. I thought I opened a bug report about it ...
[Samsung Galaxy Alpha] nuno.f.ferreira:
Well, not using no-reboot makes no difference to me. Still have protocol error and it doesn't reboot all the same. 'm seeing lots of people with this problem. It seems some kind of incompatibility with more recent samsung bootloaders. Probably we will have a new version of heimdall and/or libusbx.

JFYI, I'm using

[nunof@lucien ~]$ rpm -qa |grep heimdall

heimdall-frontend-1.4.1-2.fc22.x86_64

heimdall-1.4.1-2.fc22.x86_64

[nunof@lucien ~]$ rpm -qa |grep libusbx

libusbx-devel-1.0.19-2.fc22.x86_64

libusbx-1.0.19-2.fc22.x86_64

Would love to know why/how it works for you but I guess I'll still be using Odin one more time.

Thanks
[Samsung Galaxy Alpha] modpunk:
I'm using the latest git version ...
[Samsung Galaxy Alpha] nuno.f.ferreira:
Shoot, just tried the git://github.com/Benjamin-Dobell/Heimdall.git version and I have the same bahaviour :(
[Samsung Galaxy Alpha] nuno.f.ferreira:
Ok, after updating to these BLOBs my baseband software is still G850FXXU1COC1.

Well, there are improvements but there are also still problems with normal voice calls. Now I can still place a call, the other side can hear me fine (couldn't before) *but* I still can't hear anything (the ringing or the other side).

BT probably hasn't changed, but I'll give it a go another day.
[Samsung Galaxy Alpha] modpunk:
logcat ...
[Samsung Galaxy Alpha] nuno.f.ferreira:
Ok, this is weird and unexpected differences were found. Here's the sequence.

1. After updating the BLOBs (in reality installing stock ROM+rooting it+install TWRP+install Beta3 because Heimdall didn't work for me) I can place a call and I still hear nothing but the other side hears me cristal clear.

2. Restore my backup (System, Data, Boot) because I need a working daily phone and this is it. It's based on https://www.androidfilehost.com/?fid=24052804347813848 if you want to try to reproduce it.

3. Now I go back to installing your Beta3 (tried just installing and wipe+install and it doesn't make a difference to what I'm about to say), place a new call and I'm back to the same previous behaviour. One of two things happen:

a) Place a call and the other side listens to me with an echo about a second and then my voice goes away and it's just static. I hear nothing on my end.

or b) Place a call and the other side just hears static. I hear nothing on my end.

Attached logcat refers to 3b), sorry I don't have a logcat from 1. right now.

Is it possible that kyasu's ROM makes modem go into some state that persists across reboots?

---------- Post added at 09:55 AM ---------- Previous post was at 09:52 AM ----------

Correction: it's based on this one https://www.androidfilehost.com/?fid=24052804347809114
[Samsung Galaxy Alpha] modpunk:
When you place a phone call or a phone call comes in, you configure the soundcard to get audio from the modem and send mic input to the modem. You see this in the log:

V/audio_hw_primary( 2394): adev_set_call_audio_path: ril_set_call_audio_path(0)

V/audio_hw_primary( 2394): start_voice_call: Opening voice PCMs

ril_set_call_audio_path(0) tells the modem that we use the earpiece. There is more stuff and I need to look into that. I also saw that the modem sends infromation about the clock control. I'm not sure what to do with this information yet. There is more stuff, see https://git.cryptomilk.org/projects....git/tree/hal/audio/ril_interface.c?h=cm-12.1

and the libsecril-client source code. Most of the stuff we do is try & error to get it correct. We don't fully understand it because we do not have specs or the source code. So we need to look at similar devices and guess what we have to change for our device.

It is possible that one ROM sets something we do not handle and it keeps that state until you remove the battery for a few seconds ...
[Samsung Galaxy Alpha] modpunk:
Can you please post the output of:

cat /data/.cid.info
[Samsung Galaxy Alpha] nuno.f.ferreira:
Sure, I'll send it tomorrow morning. You need this info from a device that has succeeded in pairing or doesn't matter? From your beta3 (that can't pair) or doesn't matter?
[Samsung Galaxy Alpha] modpunk:
It doesn't matter. The file is created by the macloader (wifi) and well tell us which flavor of the wifi/bluetooth chipset you have
[Samsung Galaxy Alpha] nuno.f.ferreira:
In that case here you go: wisol