Related
I spent some hours testing files responsible for BT audio streaming from TeamEOS CM10 builds (the feature works there) on the official CM10 nightly builds.
Finally after couple of the ROM re flashes I found what file can be transfered from the TeamEOS builds to get the BT audio streaming working.
The workaround to fix the issue:
1. Download and unzip the file: http://www32.zippyshare.com/v/8042271/file.html
2. Copy the file "audio_policy.conf" to device root/system/etc
3. Reboot the Prime
Let me know if this fix works also for you.
The files are taken from the Team EOS "EOS-tf201-20120814-38" build file. Thank you guys.
Super... will check it out ASAP and will try to merge into CM10
this works... though you only need to replace ""audio_policy.conf"".... the other are not needed!!
Does that mean, the BT hasn't worked yet for CM10 or is that a fix for the known BT-bugs?
I often get BT-interruptions when streaming music to my AV-Receiver. Specially under heavy use (surfing the web for example...). Anybody else mentioning this problems?
craigacgomez said:
this works... though you only need to replace ""audio_policy.conf"".... the other are not needed!!
Click to expand...
Click to collapse
Will try with policy. conf again, first time during my tests it didn't work, probably I did something wrong that day. Thanks for feedback.
EDIT:The first post corrected as per Craig's findings
Thank you! I can listen to Pandora again
Just out of curiosity, would this also work with a touchwiz/stock version of a Rom as well? Thanks!
Sent from my SAMSUNG-SGH-I717 using Tapatalk 2
Fixed bluetooth problem, now all phone calls are on speaker phone
Sent from my SAMSUNG-SGH-I717 using xda premium
dafoxs said:
Fixed bluetooth problem, now all phone calls are on speaker phone
Sent from my SAMSUNG-SGH-I717 using xda premium
Click to expand...
Click to collapse
Tell me step by step what you did to fix the problem? I've tried this and it still isn't working for me. I'm using the latest CM10 nightly.
seems the fix has been merged in the latest build (cm-10-20120912-NIGHTLY-tf201.zip)
http://review.cyanogenmod.com/#/c/22104/
eSbek said:
I spent some hours testing files responsible for BT audio streaming from TeamEOS CM10 builds (the feature works there) on the official CM10 nightly builds.
Finally after couple of the ROM re flashes I found what file can be transfered from the TeamEOS builds to get the BT audio streaming working.
The workaround to fix the issue:
1. Download and unzip the file: http://www32.zippyshare.com/v/8042271/file.html
2. Copy the file "audio_policy.conf" to device root/system/etc
3. Reboot the Prime
Let me know if this fix works also for you.
The files are taken from the Team EOS "EOS-tf201-20120814-38" build file. Thank you guys.
Click to expand...
Click to collapse
y u no gerrit this?
Entropy512 said:
y u no gerrit this?
Click to expand...
Click to collapse
It's already merged into CM10... was submitted to gerrit by Alex on Aug 25 and merged int CM10 on Sept 11... read the thread before posting.... the previous post already said that!!
craigacgomez said:
It's already merged into CM10... was submitted to gerrit by Alex on Aug 25 and merged int CM10 on Sept 11... read the thread before posting.... the previous post already said that!!
Click to expand...
Click to collapse
For whatever reason that post wasn't displaying then... Either way, this thread should never have existed and never made it to the portal. If the maintainer had been properly contacted, it would've only been broken for a night or two.
Entropy512 said:
For whatever reason that post wasn't displaying then... Either way, this thread should never have existed and never made it to the portal. If the maintainer had been properly contacted, it would've only been broken for a night or two.
Click to expand...
Click to collapse
Well, it was a trial and error and this thread was merely created as a possible fix... when it was well tested and finalised it was pushed to gerrit just 2-3 days later... yes, it did take time for the maintainers to accept the change and merge it in CM10, but I assume they were busy...
craigacgomez said:
Well, it was a trial and error and this thread was merely created as a possible fix... when it was well tested and finalised it was pushed to gerrit just 2-3 days later... yes, it did take time for the maintainers to accept the change and merge it in CM10, but I assume they were busy...
Click to expand...
Click to collapse
This fix doesn't work anymore with latest builds of CM10.
Hi,
I have this issue.
Does anyone has solution ?
Thanks
SpySpy01 said:
Hi,
I have this issue.
Does anyone has solution ?
Thanks
Click to expand...
Click to collapse
Strange, the "fix" has been implemented in the official CM10 build, I have no problem with my bt earphones since. Are you running the official build or EOS/Craigacgomez?
The Bluetooth stream seems to be pretty good, I connected it to my cousin's Infiniti EX35 and it was seemed to lose a little bass but other than that it was a pleasant experience.
Bluetooth streaming works fine on my iPhone 5 on my 2011 maxima. On the i4S it worked good too...no issues here
...on iPhone5/iOS6 via Tapatalk...
Will this 'audio_policy. conf' fix work on any phone and CM10 flavor?
Also, I noticed that with my CM10 ROM, the native audio_policy.conf file is in a root/system/etc/bluetooth folder, not root/system/etc. Does that make a difference?
The bluetooth issues that I'm having have to do with pairing as well as tons of loud static during calls.
Thx.
Sent from my LG-LS670 using Tapatalk 2
This is for developers only. No builds will be posted in this thread.
https://github.com/CM10DNA
Any valid development related discussion can be posted here. Please no posts that aren't directly related to development (i.e. comments, thanks, etc.).
I thought I would share an update on how this very experimental code-base is doing.
The code is running again (much of yesterday it was crashing on startup).
I have been running dirty flashing from my CM 10.1 build. It seems like that was safe to do so. I tried doing a clean flash this morning but sadly, my clean flash seems to have broken cell service. No phone or data. Restoring my cm 10.1 backup of data to the same install fixed it. Strange. (This included the change pushed this morning that updates the version of the apns file).
Superuser is now working but may be a little flaky. For example, on my clean install Titanium Backup couldn't acquire root access until after I rebooted.
Camera is still not working. It says "failed to connect to camera". I haven't looked at it at all, but there is a massive commit in the M7 kernel pulling source from the HTC One Google Edition for the camera.
Overall, I'm finding it's either completely broken or working very well. I think that the cellular network issue is going to get resolved upstream. I am afraid that we might be on our own for the camera.
crpalmer said:
I thought I would share an update on how this very experimental code-base is doing.
The code is running again (much of yesterday it was crashing on startup).
I have been running dirty flashing from my CM 10.1 build. It seems like that was safe to do so. I tried doing a clean flash this morning but sadly, my clean flash seems to have broken cell service. No phone or data. Restoring my cm 10.1 backup of data to the same install fixed it. Strange. (This included the change pushed this morning that updates the version of the apns file).
Superuser is now working but may be a little flaky. For example, on my clean install Titanium Backup couldn't acquire root access until after I rebooted.
Camera is still not working. It says "failed to connect to camera". I haven't looked at it at all, but there is a massive commit in the M7 kernel pulling source from the HTC One Google Edition for the camera.
Overall, I'm finding it's either completely broken or working very well. I think that the cellular network issue is going to get resolved upstream. I am afraid that we might be on our own for the camera.
Click to expand...
Click to collapse
https://github.com/CyanogenMod/andr...mmit/ec27077d6497c66f52488126ef6b181ef3fbed0d
seems cm has stopped camera building throughout probably prepping for the focal merge
edit: idk if m7 has cam working but it hasn't been detected as a bug
"Current bugs (they are known):
SMS sending will not work (receiving works)
Dialer sub-submenu FC's the dialer
Keyboard FC's when gesture swiping"
Not sure how much this helps. But the m7 kernel recently got its camera code updated with the Google edition. http://review.cyanogenmod.org/#/c/46164/
With that so. They are able to use the 4.2 libs http://review.cyanogenmod.org/#/c/46299/
Flyhalf205 said:
Not sure how much this helps. But the m7 kernel recently got its camera code updated with the Google edition. http://review.cyanogenmod.org/#/c/46164/
With that so. They are able to use the 4.2 libs http://review.cyanogenmod.org/#/c/46299/
Click to expand...
Click to collapse
we'd probably have to merge their whole drivers/media/video/msm and use their camera binaries at least that's how it works with sense if you want to use their 4.2.2 cam libs
JoelZ9614 said:
we'd probably have to merge their whole drivers/media/video/msm and use their camera binaries at least that's how it works with sense if you want to use their 4.2.2 cam libs
Click to expand...
Click to collapse
And their commit conflicts all over the place which is going to make it hard to cherry pick it. This was the commit I referred to earlier today.
On the plus side, the ril issue looks like it will get resolved for us. There is a commit out there for Samsung hardware that adds a couple of RIL events that look like they have been added.
crpalmer said:
And their commit conflicts all over the place which is going to make it hard to cherry pick it. This was the commit I referred to earlier today.
On the plus side, the ril issue looks like it will get resolved for us. There is a commit out there for Samsung hardware that adds a couple of RIL events that look like they have been added.
Click to expand...
Click to collapse
What about the commit introducing the HTCCDMAQualcommRIL?
Sent from my HTC6435LVW using xda app-developers app
times_infinity said:
What about the commit introducing the HTCCDMAQualcommRIL?
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
Which commit?
crpalmer said:
Which commit?
Click to expand...
Click to collapse
http://review.cyanogenmod.org/#/c/45607/
Hope it helps.
Sent from my HTC6435LVW using xda app-developers app
I'll take a look at the radio stuff tomorrow. I have a couple ideas.
Deck got data working on the m7 (Sprint), check the commits or wait until tomorrow if he hasn't pushed them yet
Sent from my buttered S3
chad0989 said:
I'll take a look at the radio stuff tomorrow. I have a couple ideas.
Click to expand...
Click to collapse
To be clear, it is working fine for me if I dirty flash. I have been running 10.2 builds for 48 hours everywhere from strong wifi to bad 3G in the middle of a forest.
It's only breaking if I do a factory reset before flashing a build. That's why my guess was that it was related to this event being missing:
cyanogenmod.org/#/c/46280/1/libril/ril.cpp
(around line 2240) and that a similar change was going to be required to our libril. My inclination would be to wait and see what happens with the M7 builds (which it sounds are coming along) and see if it just magically fixes itself for us....
Edited to add: sending of text messages wasn't working but looks like they were supposed fixed last night (I haven't built it to test it yet)
crpalmer said:
And their commit conflicts all over the place which is going to make it hard to cherry pick it. This was the commit I referred to earlier today.
On the plus side, the ril issue looks like it will get resolved for us. There is a commit out there for Samsung hardware that adds a couple of RIL events that look like they have been added.
Click to expand...
Click to collapse
mm actually now that i look at it drivers/media/video/msm has been left basically untouched in our source updating to what the m7 has shouldn't be too much of a problem
JoelZ9614 said:
mm actually now that i look at it drivers/media/video/msm has been left basically untouched in our source updating to what the m7 has shouldn't be too much of a problem
Click to expand...
Click to collapse
I tried a cherry-pick before and it looked very bad. But, actually, a lot of it looks like it could be related to the comments that HTC strips from the source when the release that I added back (because it makes it easier to patch from all non-HTC sources).
If you want to take a crack at this, try doing this before cherry-picking their commit:
git show c81741a8337c2342d856ffeac0cc087452729290 drivers/media/video/msm include/media/msm_camera.h | patch -p1 -R
That will strip all the comments back out again and get rid of all those conflicts. The conflicts then look very simple (outside of arch/arm/mach-msm, which is where it gets much harder).
crpalmer said:
I tried a cherry-pick before and it looked very bad. But, actually, a lot of it looks like it could be related to the comments that HTC strips from the source when the release that I added back (because it makes it easier to patch from all non-HTC sources).
If you want to take a crack at this, try doing this before cherry-picking their commit:
git show c81741a8337c2342d856ffeac0cc087452729290 drivers/media/video/msm include/media/msm_camera.h | patch -p1 -R
That will strip all the comments back out again and get rid of all those conflicts. The conflicts then look very simple (outside of arch/arm/mach-msm, which is where it gets much harder).
Click to expand...
Click to collapse
the board-monarudo-camera.c doesn't need to be updated, at least i didn't update it in my m7 kernel port
but i can't seem to get the kernel to build
drivers/gpu/msm/adreno_snapshot.c: In function 'snapshot_rb':
drivers/gpu/msm/adreno_snapshot.c:628: sorry, unimplemented: inlining failed in call to 'parse_ib': recursive inlining
drivers/gpu/msm/adreno_snapshot.c:588: sorry, unimplemented: called from here
make[3]: *** [drivers/gpu/msm/adreno_snapshot.o] Error 1
make[2]: *** [drivers/gpu/msm] Error 2
make[1]: *** [drivers/gpu] Error 2
make[1]: *** Waiting for unfinished jobs....
i don't believe it's related to any edits i made tho heres my commit https://github.com/Joelz9614/android_kernel_htc_dlx/commit/daa90f2bf8e64a8ad6f4f497ca412bc0a77ab7ef
JoelZ9614 said:
the board-monarudo-camera.c doesn't need to be updated, at least i didn't update it in my m7 kernel port
but i can't seem to get the kernel to build
drivers/gpu/msm/adreno_snapshot.c: In function 'snapshot_rb':
drivers/gpu/msm/adreno_snapshot.c:628: sorry, unimplemented: inlining failed in call to 'parse_ib': recursive inlining
drivers/gpu/msm/adreno_snapshot.c:588: sorry, unimplemented: called from here
make[3]: *** [drivers/gpu/msm/adreno_snapshot.o] Error 1
make[2]: *** [drivers/gpu/msm] Error 2
make[1]: *** [drivers/gpu] Error 2
make[1]: *** Waiting for unfinished jobs....
i don't believe it's related to any edits i made tho heres my commit https://github.com/Joelz9614/android_kernel_htc_dlx/commit/daa90f2bf8e64a8ad6f4f497ca412bc0a77ab7ef
Click to expand...
Click to collapse
Searching in the browser doesn't have any matches for adreno_snapshot...
Maybe try git checkout -b tmp HEAD~1 and make sure that builds?
Looks like CM just merged an updated audio HAL along with the legacy HAL, both of which incorrectly detect our device for now. Building with a fix now and if all is well I'll submit upstream.
Edit: It's going to cause a bunch of routing issues again also until some other stuff gets merged in. Best to just revert their change for now for builds.
chad0989 said:
Looks like CM just merged an updated audio HAL along with the legacy HAL, both of which incorrectly detect our device for now. Building with a fix now and if all is well I'll submit upstream.
Edit: It's going to cause a bunch of routing issues again also until some other stuff gets merged in. Best to just revert their change for now for builds.
Click to expand...
Click to collapse
Aside from the routing issues, this may already be fixed for us thanks to the m7:
http://review.cyanogenmod.org/#/c/46473/
@chad0989, FYI, I reverted the commit to use legacy alsa early this morning and haven't noticed any problems (play music on Bluetooth, voice calls with and without wired headset) using that build.
You may want to give it a try and see if you're ready to revert it.
Edit: actually, I just noticed that they had also enabled legacy audio in msm8960-common but since reverted that. So, I guess I was still running the legacy mode...
crpalmer said:
@chad0989, FYI, I reverted the commit to use legacy alsa early this morning and haven't noticed any problems (play music on Bluetooth, voice calls with and without wired headset) using that build.
You may want to give it a try and see if you're ready to revert it.
Edit: actually, I just noticed that they had also enabled legacy audio in msm8960-common but since reverted that. So, I guess I was still running the legacy mode...
Click to expand...
Click to collapse
They aren't allowing new HAL to build yet (see https://github.com/CyanogenMod/android_hardware_qcom_audio-caf/blob/cm-10.2/Android.mk) But we will need that flag when they allow the new HAL to build. I added it preemptively to hopefully avoid breakage. The issue was that the legacy HAL they pushed hadn't included some changes for our CSD client and platform detection. Looking at what was committed last night/today it should work now though.
Hi, I'm trying to build CM11 for the new SGS4 device but I'm facing several issues.
I post here hoping that more people will see this than in i9506 specific forum.
First of all, I can't get hwcomposer working, the weird thing is that the GPU works great and the phone make 34000 points at AnTuTu benchmark :silly:
It also doesn't have WiFi, bt, camera nor audio..
Everything else works great, no app force closes, LTE data is good.
Here is the error logcat : http://pastebin.com/97QruUNJ
and the full logcat (in two parts because of pastebin limits) : http://pastebin.com/P0aGTpcN http://pastebin.com/ZkMLDbsi
As I can see, there is no audio because no sound card is detected, how do I configure it ?
But for wifi, bluetooth and camera, I don't see anything relevant...
Anyone already heard of this kind of problems and how to solve them ?
If you post some smaller logcat thats are actually readable I could help, just post the part where it crashes. not the entire logcat.
And this is all the problem : there is no crashes.
I can't find where all those bugs come from, and reading whole log didn't help me, that's why I posted them thinking that some devs will see things they already seen on their own ROMs
I have gotten so far in this. The device boots and operates quite normally, with three exceptions.
The camera fails to record. If it starts to record, ending the recording freezes the camera. Or, it just won't start at all.
Some graphical glitches on the lockscreen. Nothing major, or breaking, but weird (see below) but the glowpadview is missing a chunk and there's a strong line of dots towards the lock icon.
Animations are jerky.
These are the device trees I'm using
# Device Samsung i9300
https://github.com/UltimaAOSP/android_device_samsung_i9300
# smdk44121-common
https://github.com/UltimaAOSP/android_device_samsung_smdk4412-common
# Kernel source
https://github.com/UltimaAOSP/android_kernel_samsung_smdk4412
This is the AOSP tree I'm using, by broodplank1337
https://github.com/AOSP-S4-KK
The source tree is great. broodplank1337 did a great job, and it builds and runs wonderfully on the S4 i9505. I have nearly got this down but I'd appreciate any help or advice available!
@Kryten2k35 I was surprised to find no pure AOSP ROMs for SIII. I'll be getting one soon so wanted to have compiled 4.4.4 for it.
I'm surprised you get the problems you have however, as surely these aren't apparent in AOSPA, SlimKat, etc. which are based on AOSP also? Surely you must have had to add vendor/samsung stuff, maybe some hardware/ repos, etc. as missing proprietary blobs would explain the broken camera. I'd be glad to help out anyway. I was about to sync pure AOSP source but do you think this'll be too much of a challenge?
Hi,
I should've updated this thread. It turns out I was compiling with ofast CFLAGS, which was causing the graphical glitches and animation issues. The camera I haven't tested yet, but I suspect the same.
Kryten2k35 said:
Hi,
I should've updated this thread. It turns out I was compiling with ofast CFLAGS, which was causing the graphical glitches and animation issues. The camera I haven't tested yet, but I suspect the same.
Click to expand...
Click to collapse
Thanks a lot, I may as well try building my own AOSP if I know you've been successful then. Will those UltimaAOSP trees work fine for me or should I use CyanogenMods or probably better AOSPAs? I'd be grateful if you could point me towards the correct vendor tree if I'll need to use anything our of the ordinary, but I assume CMs will be fine?
Thanks and sorry for the questions but I have 0 experience with this device (don't even own it yet ) so there's many more sources, trees, and stuff than I'm used to (Desire Z only had 1 maintained device tree).
The UltimaROM trees should work fine when I update them slightly based on these changes.
Everything is mostly AOSP, with the obvious exception of the device tree and kernel tree, both of which are Cyanogen, oh, and Camera, which is also Cyanogen. I had to make a few small changes to AOSP stuff to enable it to work with the S3, as well. nothing major, though.
EDIT:
My UltimaAOSP aim is to remain as close to AOSP as possible. Any modifications are 100% optional and disabled on a new install, so a user can have a Nexus-like experience if they wish.
You are 100% welcome to download UltimaAOSP's source and help in any way you see fit. I appreciate any help I can get.
Kryten2k35 said:
The UltimaROM trees should work fine when I update them slightly based on these changes.
Everything is mostly AOSP, with the obvious exception of the device tree and kernel tree, both of which are Cyanogen, oh, and Camera, which is also Cyanogen. I had to make a few small changes to AOSP stuff to enable it to work with the S3, as well. nothing major, though.
EDIT:
My UltimaAOSP aim is to remain as close to AOSP as possible. Any modifications are 100% optional and disabled on a new install, so a user can have a Nexus-like experience if they wish.
You are 100% welcome to download UltimaAOSP's source and help in any way you see fit. I appreciate any help I can get.
Click to expand...
Click to collapse
@Kryten2k35 Thanks, although I'd love to help I'm currently working on a few of my own projetcs with other members already. Is there no need for the android_hardware_samsung repo or SamsungServiceMode any more then as I can't find them in your sources? I've synced AOSP so I'm gonna have a go with your tree right now to see if it works, is it all updated? Thanks alot
EDIT: Found those repos in your default.xml, I assume they're needed then.
EDIT2: Will I need your vendor repo too? At the moment I assume I'll just have to run lunch full_i9300-userdebug as nothing else appears to work
@HTCDreamOn
Yeah you'll need my vendor repo and my Samsung propitiatory blobs repo, I think.
I've picked back up where I left off this last few days. All the graphical glitches were fixed. But the camera glitch remains: details are here: http://forum.xda-developers.com/showpost.php?p=54234546&postcount=585
I have one choice: ArchiKernel. No other kernel works with camera recording. Which is insane, since the CyanogenMod kernel should work fine, but does not.
Hello guys and girls,
As some of you already know Android 8.1 suffers from a severe Multi-Touch Issue. This issues makes the smartphone randomly jumping between the two touching points on the screen when touching with two or more fingers.
The issue is known to google since the preview of 8.1. It isn´t only affecting pixel but most probably all devices running 8.1. The issue is also present on P.
An issue got created here: https://issuetracker.google.com/issues/70344455
There is a fix since mid march in review on google gerrit. But that didn´t make it into the april release, obviously.
To visualize the issue refer to the following videos:
https://youtu.be/wgYN5GwIgIc
https://youtu.be/2Vv584tvVyg
https://www.youtube.com/watch?v=4dnIk_5qdK8&feature=youtu.be
This is especially bad for gamers. With the recent release of PUBG this issues seems dramatic to some, less to others.
I´m no gamer but I noticed the issue on the google foto app.
This issue has nothing to do with the corners badly reacting to touches, or touch sensitivity etc.
So but now to the fix. It seems the issues is only related to resampling but not to touching specific points of the screen ( not related to crossing x and y axis).
That also explains why the issue wasn´t happening when using the touch tracking tool in dev settings but on various multi touch test apps.
The fix is on google gerrit currently under review here:
https://android-review.googlesource.com/c/platform/frameworks/native/+/640605
https://android-review.googlesource.com/c/platform/frameworks/native/+/640606
Last week I compiled myself a DU build with the changes included and I couldn´t trigger the issue at all. I found no other side effects caused by the two patches.
For now I decided to provide a Magisk Module which replaces the changed libs that fixes the issue.
I compiled the libs while doing my april build of DU. The magisk module can be found on the link a little bit down.
The download is here:
https://www.androidfilehost.com/?fid=890129502657595755
A few disclaimers here.
1. That fix should in theory work for most 8.1 devices, including the likes of pixel 1st gen, pixel 2nd gen, one plus, xiaomi which suffer from this severe issue.
2. I didn´t fix this, I just compiled the libs with the fix found on google gerrit.
3. Rom devs you are very welcome to include this fix. I found no ill consequences as of yet but I can understand google taking it slow and reviewing it longer. Maybe they will find a better fix, but as of now this is the best thing we have.
Donations:
Donations are not mandatory but very welcome.
If you like my work: http://paypal.me/freak07
I've got Joe's DU right now, will this affect me?
kingbri said:
I've got Joe's DU right now, will this affect me?
Click to expand...
Click to collapse
Check his git to see if he pulled the fix in or not
Updated trees today I'll push tomm
Just installed on latest lineage .. it's perfect!! Thank you so much
Any word on a fix for the sound bug on 8.1? After a couple of hours the phone stops playing ringtones and notifications (while other sounds work ala YouTube Spotify). A reboot fixes it temporarily.