@Flohack I do not actually have this issue, but I haven't tested my music app yet so that may be why
Posts made by user
-
RE: Call for testing: Google/Huawei Nexus 6P (angler) owners
-
RE: Call for testing: Google/Huawei Nexus 6P (angler) owners
@Flohack Thank you very much, yeah It seems a lot more complicated than I initially bargained for, but I don't mind taking a deep dive into the guts of the system. I haven't got much else better to do
I'll let you know if I make any headway
-
RE: Call for testing: Google/Huawei Nexus 6P (angler) owners
@Flohack I'm trying to hack my way into the device to figure out how to get an audio stream for the calls. Could you point me in the right direction with how telephony and audio work?
It seems that the phone uses ofono for calls and pulseaudio for audio, but getting them to play together hasn't been at all fruitful.
-
RE: Call for testing: Google/Huawei Nexus 6P (angler) owners
@Flohack 21 ms ping, 17.96 MBPS down
-
RE: Call for testing: Google/Huawei Nexus 6P (angler) owners
@Girlycard777 don't know if you saw this yet, but helpful when setting up
http://pad.ubports.com/p/nexus-6p-alphatesting -
RE: Call for testing: Google/Huawei Nexus 6P (angler) owners
I grepped 'pulse' in var/log/syslog and got this for the time that I was trying to make a phone call:
8 13:48:35 ubuntu-phablet pulseaudio[2626]: [pulseaudio] sink.h: Assertion 'pa_object_refcnt(pa_object_cast(o)) > 0' failed at ./pulsecore/sink.h:306, function pa_sink_assert_ref(). Aborting. Jul 8 13:48:36 ubuntu-phablet pulseaudio[7983]: [pulseaudio] pid.c: Stale PID file, overwriting. Jul 8 13:48:36 ubuntu-phablet pulseaudio[7983]: [pulseaudio] droid-util.c: Requested sample rate 44100 but got 48000 instead. Jul 8 13:48:36 ubuntu-phablet pulseaudio[7983]: [pulseaudio] sink.c: Default and alternate sample rates are the same. Jul 8 13:48:36 ubuntu-phablet pulseaudio[7983]: [pulseaudio] droid-util.c: Requested sample rate 44100 but got 48000 instead. Jul 8 13:48:36 ubuntu-phablet pulseaudio[7983]: [pulseaudio] sink.c: Default and alternate sample rates are the same. Jul 8 13:48:36 ubuntu-phablet pulseaudio[7983]: [pulseaudio] module-droid-discover.c: Device has AudioFlingerglue Jul 8 13:48:36 ubuntu-phablet pulseaudio[7983]: [pulseaudio] droid-util.c: Failed to open output stream: -17 Jul 8 13:48:36 ubuntu-phablet pulseaudio[7983]: [pulseaudio] droid-sink.c: Failed to open output stream. Jul 8 13:48:36 ubuntu-phablet pulseaudio[7983]: [pulseaudio] droid-util.c: Failed to open output stream: -17 Jul 8 13:48:36 ubuntu-phablet pulseaudio[7983]: [pulseaudio] droid-sink.c: Failed to open output stream. Jul 8 13:48:36 ubuntu-phablet kernel: [ 109.700560] pulseaudio[7983]: syscall 389 Jul 8 13:48:36 ubuntu-phablet kernel: [ 109.700597] CPU: 0 PID: 7983 Comm: pulseaudio Not tainted 3.10.73-g45457ef #12 Jul 8 13:48:36 ubuntu-phablet pulseaudio[7983]: [pulseaudio] main.c: Sink sink.primary does not exist. Jul 8 13:48:36 ubuntu-phablet pulseaudio[7983]: [pulseaudio] main.c: Source source.primary does not exist.
not sure if this is very helpful for troubleshooting the phone audio issues.
-
RE: Call for testing: Google/Huawei Nexus 6P (angler) owners
I can make calls, but audio doesn't seem to be getting transferred. No sound on either device when i phone.
The selfie cam works but the image appears distorted. not a big issue.
There doesn't seem to be any integration for the fingerprint reader as well.
-
RE: Call for testing: Google/Huawei Nexus 6P (angler) owners
just tested camera, works well. no issues.
-
RE: Call for testing: Google/Huawei Nexus 6P (angler) owners
finally got it up and running, will try it out soon
-
RE: Call for testing: Google/Huawei Nexus 6P (angler) owners
try going into the flash-all.sh script and take out the -w flag on the last command then run it again?
-
RE: Call for testing: Google/Huawei Nexus 6P (angler) owners
@user For posterity:
I was using lineageOS prior to this, there was an issue flashing back to android. namely, mke2fs failed because unimplemented ext2 function while setting up superblock
quick google search said I need to go into the flash-all.sh and edit it.
I had to change the last line from fastboot update -w <image.zip> to fastboot update <image.zip>
the -w flag is to wipe userdata and cache.
So far, the image seems to be flashing without issues.
-
RE: Call for testing: Google/Huawei Nexus 6P (angler) owners
@Flohack Thanks for that info, I'll keep to 8 core for now in that case and reflash 7.1.2 and try again
-
RE: Call for testing: Google/Huawei Nexus 6P (angler) owners
@rocket2nfinity Thanks, I may not have successfully managed to flash the android image for some reason, so that could be the problem. I'll also make sure that my twrp is 4 core and I'll use the 4 core halium to see if that helps.
-
RE: Call for testing: Google/Huawei Nexus 6P (angler) owners
Hey everyone, so I've decided to try as well.
So far, I've managed to flash the image to my 6p. It apparently boots up because I can ssh into it. However, the phone itself is stuck on the Google screen. I ran dmesg -w on the phone and get this happening in a loop:
[ 91.664666] init: Starting service 'perfd'...
[ 91.667370] init: Starting service 'time_daemon'...
[ 91.668649] init: Starting service 'qcamerasvr'...
[ 91.671437] init: Starting service 'ril-daemon'...
[ 91.672204] init: Starting service 'fps_hal'...
[ 91.716873] init: Service 'ril-daemon' (pid 1405) exited with status 1
[ 91.716895] init: Service 'ril-daemon' (pid 1405) killing any children in process group
[ 91.766425] init: Service 'qcamerasvr' (pid 1404) killed by signal 6
[ 91.766451] init: Service 'qcamerasvr' (pid 1404) killing any children in process group
[ 91.770755] init: Service 'per_proxy' (pid 1399) killed by signal 6
[ 91.770779] init: Service 'per_proxy' (pid 1399) killing any children in process group
[ 91.771072] init: Starting service 'per_proxy'...
[ 91.858763] init: Service 'per_mgr' (pid 1398) killed by signal 6
[ 91.858794] init: Service 'per_mgr' (pid 1398) killing any children in process group
[ 91.946013] init: Service 'thermal-engine' (pid 1400) killed by signal 6
[ 91.946044] init: Service 'thermal-engine' (pid 1400) killing any children in process group
[ 92.030662] init: Service 'perfd' (pid 1402) killed by signal 6
[ 92.030687] init: Service 'perfd' (pid 1402) killing any children in process group
[ 92.143446] init: Service 'time_daemon' (pid 1403) killed by signal 6
[ 92.143493] init: Service 'time_daemon' (pid 1403) killing any children in process group
[ 92.257922] init: Service 'qmuxd' (pid 1401) killed by signal 6
[ 92.257962] init: Service 'qmuxd' (pid 1401) killing any children in process group
[ 92.344606] init: Service 'fps_hal' (pid 1407) killed by signal 6
[ 92.344638] init: Service 'fps_hal' (pid 1407) killing any children in process group
[ 92.451645] init: Service 'per_proxy' (pid 1417) killed by signal 6
[ 92.451680] init: Service 'per_proxy' (pid 1417) killing any children in process groupI'm not sure if this has anything to do with the problem I'm facing or if I just need to send some signal to the device while ssh'd in. any ideas?