Database Info

New CM10.1 Audio HAL for Steelhead Amplifier

I have been using my Nexus Q for about a year via the audio amplifier outputs. When the last Music update broke Q functionality, I decided to give CM10.1 a try on the Q. After fighting some installation issues, where all audio output except "Alarms" were silenced, I found that audio is only working on the HDMI output.
After digging through the code and doing a bit of analysis of the stock Audio HAL, I figured out how to make an audio HAL that supports the TAS5713 audio amplifier used in the Q. As of now, it only supports one audio output device (either HDMI, S/PDIF, or TAS5713) at a time, and the output can only be changed during compile time.
But with some work, this HAL could eventually support all three outputs (HDMI, S/PDIF, TAS5713.) The issue is that Android only appears to support one output device at a time. In order to overcome this, I believe the audio HAL would have to replicate the PCM data stream and send a separate copy to each device.
Through experimentation, I found that the TAS5713 requires a 48KHz audio stream, and S/PDIF also works well with this rate.
Another challenge is that the TAS5713 amplifier volume is controlled by the kernel driver, so you have to tell Android that the Audio HAL will do the volume control itself (ie, not rely on the mixer in Android.) For this reason, if all three output devices are eventually supported, volume control for S/PDIF and HDMI would have to be done in software. Perhaps it can be done while duplicating the PCM stream by taking each of the 16-bit values and multiplying it by the volume level.
Looking through the Steelhead kernel, you can see that Google put some work into being able to synchronize the three audio output devices. This would also have to be added to the HAL for proper operation.
Anyway, I'm putting the changes out there in GitHub in case someone wants to do some more improvement to this audio HAL.
The fork of CyanogenMod/android_device_google_steelhead is hharte/android_device_google_steelhead:
https://github.com/hharte/android_device_google_steelhead
For binaries that you can flash to your Q (TAS5713 audio amplifier and S/PDIF) please scroll down to post #9 and choose the correct binary. Each binary only supports one audio output.

Please make this a reality.. I'm dying to have the analogue outputs working at the same as HDMI. it was possible on the stock Nexus Q image.

Thank you for the work you've put into making this a reality. I would love to try out a build with the amplifier selected as the output device, but it sounds like you can't control the volume natively?
Sent from my Nexus 4 using Tapatalk 2

Thanks for doing this!
After cloning your repository, I wasn't sure what to modify to have audio output through S/PDIF or TAS5713. Would you mind giving some advice to someone new to building CM?
Thanks in advance.

mahler47 said:
Thanks for doing this!
After cloning your repository, I wasn't sure what to modify to have audio output through S/PDIF or TAS5713. Would you mind giving some advice to someone new to building CM?
Thanks in advance.
Click to expand...
Click to collapse
In device/google/steelhead/audio/audio_hw.c, change the following line in the function adev_open():
adev->card = CARD_STEELHEAD_TAS5713;
Change CARD_STEELHEAD_TAS5713 to one of:
CARD_STEELHEAD_HDMI,
CARD_STEELHEAD_SPDIF,
CARD_STEELHEAD_TAS5713
Volume control should work fine for each of these, based on my last commit:
https://github.com/hharte/android_d...mmit/a15f772b5651e0b14c65f6ff1a6d498d2951e081
Then "brunch steelhead" to re-build CM10.1 for Nexus Q. After it is done building, you can go into out/target/product/steelhead/ and do "fastboot -w flashall" to wipe and flash the new CM image. If you are making minor mods, no need to use "-w" to wipe.
Please let me know if you find any issues. One of the main things I've struggled with when using CM10.1 on Nexus Q is that sometimes after installing gapps, the audio is completely silent. I have not found a good way to fix this other than downloading and installing "Audio Manager" from the Play Store.
-Howard

Howard, YOU ROCK!
This is amazing. My Nexus Q is nearly back to the functionality that I once had with stock firmware, and it's once again a useful device.
Here's my setup:
1) 2013-06-12 nightly build with your changes merged, and as instructed above, audio sent to S/PDIF. My Q is connected to the stereo via optical cable.
2) VNC Server is installed on the Q, and it turns on upon boot. I am using this VNC Server, but I bet others would work.
https://play.google.com/store/apps/details?id=com.schumi.vncs
3) I also have FTP server and ADB Wireless turned on upon booting so I can push files and mess with the Q remotely.
4) VNC Viewer installed on my other devices.
With all of that, I can basically control the Q remotely from my phone, tablet, or computer. VNC is slow, even with a wired connection, but it works.
Prior to your good work, I had to have the TV on to hear anything out of my Nexus Q. However, with the changes you've implemented, I no longer have to do that. My Q lives again!! :victory:
Thanks so much--things can only get better and better from here. This is exactly why the Android community is so amazing.

mahler47 said:
Howard, YOU ROCK!
This is amazing. My Nexus Q is nearly back to the functionality that I once had with stock firmware, and it's once again a useful device.
Here's my setup:
1) 2013-06-12 nightly build with your changes merged, and as instructed above, audio sent to S/PDIF. My Q is connected to the stereo via optical cable.
2) VNC Server is installed on the Q, and it turns on upon boot. I am using this VNC Server, but I bet others would work.
https://play.google.com/store/apps/details?id=com.schumi.vncs
3) I also have FTP server and ADB Wireless turned on upon booting so I can push files and mess with the Q remotely.
4) VNC Viewer installed on my other devices.
With all of that, I can basically control the Q remotely from my phone, tablet, or computer. VNC is slow, even with a wired connection, but it works.
Prior to your good work, I had to have the TV on to hear anything out of my Nexus Q. However, with the changes you've implemented, I no longer have to do that. My Q lives again!! :victory:
Thanks so much--things can only get better and better from here. This is exactly why the Android community is so amazing.
Click to expand...
Click to collapse
Glad to hear that it is working for you. I'm using AirBubble and Bubble uPnP apps on my Q along with "Remote for iTunes" on my phones/tablet. This allows me to actually use my iTunes library on the Q remotely, and DLNA as well.
What needs to be done next (but not sure when I will have time to do it) is to make some changes to the Audio HAL to replicate the audio stream for each output (HDMI, Amplifier, S/PDIF) and implement software volume control for the HDMI and S/PDIF.
Another really cool thing would be to be able to make the Q into a Bluetooth A2DP sink. Then you could pair it to your phone and use it as a set of bluetooth speakers.
Google obviously put a lot more effort into the Q than I have done (making a remote management app that is simple to use, and put a lot of work into making sure that the three audio outputs are synchronized.) So there is a lot more work that needs to be done.
Maybe eventually Cyanogenmod can take my audio HAL. At least it seems to be working as well as the one included in the CM10.1 nightly, and adds the choice of using the other audio outputs, although only as a compile option unfortunately.

I'm embarrassingly uninformed about the inner workings of Android, but is ALSA in Android in any way like it is in Linux? Because I think in Linux when you use ALSA to configure your sound devices and let's say you use Pulse Audio, you have to define in the ALSA config which devices to output sound to and also expose them somehow to the PA mixer. It sounds like what you're doing is only compiling one alsa module whereas a HAL more like the one Google's would be 3 separate modules, right? And then I have no idea how the Android mixer works, but in Linux you'd have a master slider that would control the digital sound and then separate sliders for each output device. Is that sort of behavior replicable in Android?
On a different note, I'm really really sorry to beg because I'm so close to getting a CM build environment set up for the first time, but could either of you gentleman upload a working TAS5713 build? I feel pathetic because it's taken me 2 days just to get a VM image set up on my wife's laptop and most of the CM repo synced and I just *know* that this rom is going to take hours to compile (assuming I was competent enough to set it up right and create a proper manifest). Once/if I get everything set up, I think I'm going to go ahead and commit to merging your amazing work with CM10.1 final when it's out and uploading the zip so that all 5 of us Nexus Q owners out there don't each have compile it from source, but for now, I'd appreciate any help y'all can give me

Malnilion said:
On a different note, I'm really really sorry to beg because I'm so close to getting a CM build environment set up for the first time, but could either of you gentleman upload a working TAS5713 build? I feel pathetic because it's taken me 2 days just to get a VM image set up on my wife's laptop and most of the CM repo synced and I just *know* that this rom is going to take hours to compile (assuming I was competent enough to set it up right and create a proper manifest). Once/if I get everything set up, I think I'm going to go ahead and commit to merging your amazing work with CM10.1 final when it's out and uploading the zip so that all 5 of us Nexus Q owners out there don't each have compile it from source, but for now, I'd appreciate any help y'all can give me
Click to expand...
Click to collapse
Hello,
Here is a build of CM10.1 from repo sync on 6/17/2013 for each of TAS5713 and SPIDF outputs:
These files ar enow being hosted at AndroidFileHost
TAS5713 (Audio Amplifier):
Download: https://www.androidfilehost.com/?fid=95784891001602467 (148MB)
MD5SUM: adc98db7a9905b89c0d2fa9eab601f58 *cm-10.1-20130617-UNOFFICIAL-steelhead_TAS5713.zip
SPDIF:
Download: https://www.androidfilehost.com/?fid=95784891001602468 (148MB)
MD5SUM: ec26a86a5011cf480a9efb3cee63e000 *cm-10.1-20130617-UNOFFICIAL-steelhead_SPDIF.zip
HDMI: Use stock CM 10.1 nightly build.
Note: If, after installing, you don't have any sound, then install gapps and download "Audio Manager" from the Play Store. Run Audio Manager and select the "Mute" profile, and then select the "Loud" profile.
To install:
Boot into recovery mode:
Code:
fastboot boot recovery.img
When Q has reached recovery mode, push the cm-10.1-....zip to /sdcard using adb, ie:
Code:
adb push cm-10.1-20130617-UNOFFICIAL-steelhead_TAS5713.zip /sdcard/
push gapps (if desired) to /sdcard/
gapps-20130301.zip http://goo.im/gapps/gapps-jb-20130301-signed.zip md5: b7e53e96e1c8b1a1c4865bf29418c8e0
From within recovery, "install zip from sdcard" and browse to cm zip file. After this has installed, it is a good idea to wipe data and cache. Then install gapps (if desired) by again choosing "install zip from sdcard" and choosing the gapps .zip file.
If cm10.1 gets stuck in a boot loop, then you probably forgot to wipe. Reboot the Q back into fastboot as follows:
Unplug power for Nexus Q and wait about 10 seconds.
Plug Q back in.
When the LED lights up on the top of the Q, cover it with your hand until the LED ring turns red. This has to be done in less than one second. If you miss it, try again.
As soon as the ring is RED, remove your hand, and the Q should be in fastboot mode.
Now, you can "fastboot -w" to wipe, or "fastboot boot recovery.img" to boot into recovery and wipe using the menu.
Please let me know how these work for you. I'm using these TAS5713 and SPDIF builds now and they are working fine for me.

Thank you so much! My foray into rom building was initially a disaster. I got what I thought was a good virtual image built and configured, but then I found out a fundamental error on my part...I had built a 32bit image. So, I finally just installed Ubuntu on a system partition and finally yesterday built my first stock CM image. I'm going to keep going so I can build for myself, but at least now I can listen to my music on my nexus q speakers while I'm working
Your build is working just great for me. The only times I've had volume issues on stock, I just had to wiggle the nexus q top and tap mute/unmute a couple times. I don't know if your HAL is any different or not yet, but so far, so good! Thanks again!
Edit:
I've mirrored your files and intend for this to be the place I'll put my builds in the future. I'm fairly sure Google Drive doesn't have bandwidth limits, so anybody reading...have at it!
Sent from my Nexus 4 using Tapatalk 2

Make sure you have plenty of RAM in your VM. I'm building on a Mac Pro running Ubuntu (not in a VM) and it takes about 35 minutes to build.
Tried once in a VM running under Windows and killed it after about a day... but the VM only had 1GB of RAM allocated to it.

Thank you so much for the amplifier-build! Just installed it and my Q is better than before. For everybody who wants to re-use the Q as a music player, I can really recommend bubbleupnp. It directly accesses your Google Cloud Music and makes it available via DLNA to other devices
Just install it on the Q and on your tablet / or phone. On the device you want to use as a remote, you can select which media server (Nexus Q) and which media renderer to use (Nexus Q). And - bam - you have your Q back. Browse your media from the phone and play it directly from the Q. Bubbleupnp even has an option for autostart, so once everything is setup, you don't have to use keyboard / mouse / monitor.
The DLNA thingy also has another neat side-effect: The Q now is recognized in Windows 8 as a dlna-device and you can browse you entire Google Music Library with the Windows Explorer and play stuff to your Q...
Guess someone's happy his little gadget is back...
Again. THANK YOU for your awsome work on the Q.

New Life for the Q
[Solved]: was using an HDMI to digital converter cable. Hooked it up to my TV and everything worked great.
First, I would like to say.... this is great! I thought the Q was done.
I'm having some trouble with the install. I was able to push everything to the device, booted into recovery, followed your instructions in flashing CM10.1 and gapps.... and then all I got was the orb sitting there with its blue light and no video. I've messed up flashing roms on other android devices so I thought I would pop back into recovery and try another shot at flashing CM10.1 without gapps. I boot into recovery, the light on the Q keeps spinning (which is what I remember) but there is no video! I know I am in recovery because I can top the Q and it reboots (first option in recovery). What can I do?
thank you,
Tony

Awesome work, thank you !
This is exactly what I was looking for.
Thank you also for the idea of using bubbleupnp, it seems that the new functionality will be better than the original.
I can hardly wait to re-image my Q.

Thanks a million for sharing your work! Works like a charm for me with the SPDIF build.

Bullet91 said:
Thanks a million for sharing your work! Works like a charm for me with the SPDIF build.
Click to expand...
Click to collapse
Op we need ypour help if you would mind updating this to the newest nightly and giving a little support I will kick you some money I emailed you too since you are the only one who has gotten the amp to function.

Thanks for the work you have put in, but every time i try to download the TAS5713 version it is not the 148mb you post says and does not have a matching md5sum.
Can someone host their working TAS5713 build for me?

unknownkwita said:
Thanks for the work you have put in, but every time i try to download the TAS5713 version it is not the 148mb you post says and does not have a matching md5sum.
Can someone host their working TAS5713 build for me?
Click to expand...
Click to collapse
Yes the build I downloaded doesn't work either.

im hosting the rom Anthony uploaded in this g+ post. To the best of my knowledge it is the TAS5713 CM10.1 rom that was originally modified by hharte. Ill keep it up for the foreseeable future. I TAKE NO RESPONSIBILITY FOR ANYTHING.
https://docs.google.com/file/d/0B8a2mhiG243Ja1lqc0xVQzAwdjQ/edit?usp=sharing

ianandamy said:
Yes the build I downloaded doesn't work either.
Click to expand...
Click to collapse
Are you flashing the AMP build provided in this post? http://forum.xda-developers.com/showpost.php?p=42690346&postcount=9
For me it is the SPDIF build which is working, I did not test the AMP one.

[APP][AOSP Root 4.4] AudioTricks / VolumeTricks

Thread is under construction.
WARNING: There have been 3 reports so far of failure to boot after installing the Shim HAL. This sort of problem should be assumed possible at this early "Alpha level research project" phase.
Please don't install if you have stock recovery or don't know what recovery is.
Please don't install if you are nervous. Wait a while for the bugs to get worked out and info compiled.
Don't install if not confident in your technical skills.
Don't install if you might freak out if your phone gets disabled for a little while.
For bootloops or to fix or remove: http://forum.xda-developers.com/showpost.php?p=52931431&postcount=67
Post #2 has download links and instructions: http://forum.xda-developers.com/showpost.php?p=52765309&postcount=2
Since interest has ramped up quickly, I've published a 99 cent "donate" version on Play: https://play.google.com/store/apps/details?id=fm.a2d.av (Wait until the $200 placeholder price disappears, LOL.)
I'm not sure "donate" is the right word, but it's the exact same app I'm distributing and will continue to distribute for free (for at least X months to a year ??), so nobody is under any obligation to buy to get the app. Updates will be automatic via Play though.
============================================================
AudioTricks / VolumeTricks is a new kind of "audio mod" that is HAL Shim based.
At present, it can raise or lower output volume and microphone input gains digitally.
Only works on ICS Android 4.0.3 and later. AOSP ROMs such as CM11 or other KitKat very much preferred. Many stock ROMs 4.1-4.3, won't work, especially HTC.
Post 2 has download link and instructions.
Disclaimer: Please understand that this is the first public release of this app. Although I endeavour to make my apps as safe as possible, one never knows whether or not some silly bug or unusual interaction might pop a speaker, headset or whatever. I have over 20 devices that I use for testing my apps and I try to "torture test" as much as possible. So if something goes pop, I'll be very sorry and do everything I can to analyze and fix any problems. If you're "not sure", just wait and more adventurous people will do the early testing needed to help ensure nothing breaks.
By it's very nature, any app that can boost volume creates risk for audio output devices as well as your ears.
For those who know my Spirit FM apps, this is a bit of a move for me. Spirit1 and Spirit2 both are alive and well, but the future of FM radio on Android seems to be dimming the last few years. I'll be splitting my time between apps based on the support I get.
Making this HAL Shim based provides some advantages and disadvantages over other methods of changing volume or gain.
Advantages include:
- Audio modification even for apps, games, etc. that use the low level Android NDK OpenSL ES API.
Disadvantages:
- Analog controls, if available, may be better.
AudioTricks is intended to be my name for a group of small apps, and/or a "master app" that includes the features of them all.
VolumeTricks is the first such small app to be released, and is focused on output volumes and input gains.
VolumeTricks may not be limited to the "HAL Shim" approach to audio mods. It may also include ALSA, ALSA UCM, and other methods to manipulate audio.
At this time, the app is free, but Copyright Me. I'll likely maintain a free version for some time, but I gotta eat too so there will be a paid version on Play when it seems ready.
At this time, this app has been tested mostly on CM11 and a few other AOSP ROMs. Many stock ROMs won't work, especially HTC.
The app is currently set to only work on Android KitKat 4.03+.
I haven't tested ART much yet, mostly Dalvik, but it's working OK on my One M7 w/ ART. Shouldn't be too hard to fix any ART issues.
So what the heck is a "HAL Shim" ??
Android uses HALs (Hardware Adaptation Libraries) as an API between Google's Android code and the phone OEMs hardware specific code. Android Audio has at least 2 HALs, one for "Policy" (selects outputs, inputs and some other stuff) and one for the audio transfers. The HAL Shim in this app works with the latter "Primary" HAL for audio transfers.
A SHIM is a component that sits between 2 other components and pretends to be the higher component as well as the lower component. Hierarchy:
Android AudioFlinger
------------------------
HAL Shim
------------------------
Primary Audio HAL
So, the HAL shim pretends to be an audio HAL to Android's AudioFlinger. AND it pretends to be Android AudioFlinger to the Primary Audio HAL.
The HAL shim acts as an intermediary. It can pass everything back and forth unmodified which makes it invisible. Or it can modify anything passing between, including the audio data.
Isn't there a better way to do this ? No, I don't think so. I don't want to be modifying a bunch of HALs on thousands of ROMs. I also don't want to be modifying AudioFlinger on those same hordes of ROMs.
What else can be done with the HAL Shim concept, besides "Volume Tricks".
I think some of these may be feasible:
- Recording all inputs and/or outputs. Maybe even both sides of phone calls.
- Analyze, Visualize, Equalize, Effects-ize all or many inputs and outputs.
- Bypass DRM.
- Maybe a method to modify (eg. encrypt / decrypt) phone call audio, inbound and outbound; possibly via pretending to be a BT headset....
Note that, at present, the HAL shim only works with the "Primary Audio Interface". Small-ish mods could do the same for HDMI, A2DP / BT, USB Audio, "Remote Submix" and whatever new audio devices Google defines.

Post 2 download link and instructions.
If a boot loop would ruin your day, please see warnings at top of post #1 and don't install this app until more mature.
Disclaimer: Please understand that this is the first public release of this app. Although I endeavour to make my apps as safe as possible, one never knows whether or not some silly bug or unusual interaction might pop a speaker, headset or whatever. I have over 20 devices that I use for testing my apps and I try to "torture test" as much as possible. So if something goes pop, I'll be very sorry and do everything I can to analyze and fix any problems. If you're "not sure", just wait and more adventurous people will do the early testing needed to help ensure nothing breaks.
By it's very nature, any app that can boost volume creates risk for audio output devices as well as your ears.
Android seems to have a ridiculously / hilariously complex audio system... LOL.
v140530: http://d-h.st/2lc#.U4hLA3KBugY
Fixes a LOT of issues, especially SU / mount issues with stock restrictive SELinux like Samsung stock 4.2+.
As always, Press Update/OK to update Shim HAL each new release.
- SU / root fixes, especially for SELinux Samsung 4.2+.
- Fine control removed.
- Coarse control range changed from -60 to +60 db ; now 0 to +36 db. Maybe I'm the only one w/ a need for gain reduction below 1.0 or 0 dB.
- Many other fixes.
Version av-140526:
- Fix the /system/addon.d/ ROM update backup/restore script used during ROM updates.
Version av-140525:
- Automatic gain reduction is now sticky, so reduces distortion when maxed. Touch sliders to reset.
- Numbers for VU.
- After amplification VU display.
- Sliders caiibrated in dB.
May not work on stock ROMs, especially older Android versions and HTC stock ROMs.
Starting this app for the first time should request root and prompt to install the HAL Shim and an addon.d backup/restore script to allow it to survive ROM updates.
After the Shim is installed, the "system_server" is killed in order to activate the Shim. Sometimes it may be better to completely reboot the phone, especially with effects, visualizers and player apps running at install time.
Once the app and Shim are installed, the app shows a "Remove" button that removes the Shim, should it be causing you problems or you just don't want/need it. The button will change to "Update" with newer versions of the app/Shim.
Sometimes, like on ROMs with old Legacy HALs, state detection won't work and the button will only offer to Install with no way to remove. As of v1.0.3 go to the 2nd tab (swipe from right to left) and there is a permanent Remove button.
If you remove the app without removing the Shim, the shim will remain, but should be mostly dormant. The easiest way to remove the Shim would be to reinstall the app and select the Remove button.
To manually remove the Shim and addon.d script, something like this should work from a connected PC with adb shell:
Code:
adb shell
su
mount -o remount,rw /system
ll /system/lib/hw/audio.primary.*.so
# !!!! Note the name of the HAL, like audio.primary.msm8960.so and use this name in next line. (If only audio.primary.default.so exists, use that.)
mv /system/lib/hw/audio.primary.orig.so /system/lib/hw/audio.primary.msm8960.so
rm /system/addon.d/99-audiotricks.sh
mount -o remount,ro /system
reboot
Using the app:
See post #3 for usage instructions.

Usage:
If a boot loop would ruin your day, please see warnings at top of post #1 and don't install this app until more mature.
Disclaimer: Please understand that this is the first public release of this app. Although I endeavour to make my apps as safe as possible, one never knows whether or not some silly bug or unusual interaction might pop a speaker, headset or whatever. I have over 20 devices that I use for testing my apps and I try to "torture test" as much as possible. So if something goes pop, I'll be very sorry and do everything I can to analyze and fix any problems. If you're "not sure", just wait and more adventurous people will do the early testing needed to help ensure nothing breaks.
By it's very nature, any app that can boost volume creates risk for audio output devices as well as your ears.
To select output volume or input gain, swipe left or right or use the tabs. The primary/left screen is for output volume.
Set the enable switch to ON to enable volume/gain adjustments.
The Left and Right indicators are logarithmic/DB audio level indicators, updated every 0.1 seconds with the peak audio level. These show the signal level before amplification. If they are VERY near the full width of the screen, there is little amplification that can be reasonably done. (But 80-90% leaves some room, given the exponential nature.)
For no boost, IE an amplification factor of 1.0, the Coarse and Fine controls should both be set to 0 at centre.
Setting Fine all the way right to +6 dB doubles audio power, setting to -6 dB halves audio power.
Setting Coarse to +30 dB creates an amp factor of 32, assuming Fine is set to 0. Setting -30 dB is about 0.03.
Note that an amp factor of 32 is very high, unless you are dealing with very low input signals.
The Shim detects when the signal will overload, and reduces the amp factor as needed to prevent overload/distortion. To raise it again, use the UI to reset.
There are some "streams" for which amplification will not work. I will support as many stream flags (such as Fast) as I can; remains to be seen; this is still kind of a "research project" at this stage.
At present, all streams are amplified the same amount. Per stream or stream type amp factors will be supported.

Just go to post #11 on next page.

Nothing to see here, move along.

Technical info to fill in later.
Pay no attention...

... to the man behind the curtain...

8 is lucky 7 + 1; even better.

Trouble-shooting info.

#10 is always "Future".

Comments and questions start here.

Volume control?
Hi Mike,
You are making me curious about this new project of you.
I bought a long time ago this app for level control. It is doing his job, but has lack of storing the settings and sometimes still adjust (unwanted) the volume.
Count me in for testing :fingers-crossed:
Edit: get an error parsing the apk :crying:

Rinoceros said:
Hi Mike,
You are making me curious about this new project of you.
I bought a long time ago this app for level control. It is doing his job, but has lack of storing the settings and sometimes still adjust (unwanted) the volume.
Count me in for testing :fingers-crossed:
Edit: get an error parsing the apk :crying:
Click to expand...
Click to collapse
Welcome to my new thread and app.
AFAICT, that app mostly just manipulates standard Android volume levels, which is fine, but not much different than the standard volume control.
I just downloaded my new app linked http://d-h.st/plb myself (7 downloads in first 2 hours now), and it installs fine on my One M7, and matches bit for bit the 1.0 version installed on my test phones.
So you're on stock based InsertCoin ROM ?
As long as it's Android 4.4 KitKat (API Level: 19), it SHOULD parse and install OK.
The binaries are for ARM devices only (ie 99+% of Android devices). Intel x86 or MIPs can't work (at present.)
I can't think of any other reason it won't parse, unless your copy is corrupted. This is the MD5 I get:
Code:
md5sum ~/Downloads/av-release.apk
2c8328e8cbe1f585f3b1634e36200c8f /home/mike/Downloads/av-release.apk
I'm happy to hear anyone else's stories of success or failure, but I'll need a good 7 hours of sleep first.
------------
Happy Victoria Day to all fellow Canadians & CommonWealther's, and Good Long Weekend to all those with a day off of work this Monday. Finally nice weather here lately...

mikereidis said:
I just downloaded my new app linked http://d-h.st/plb myself (7 downloads in first 2 hours now), and it installs fine on my One M7, and matches bit for bit the 1.0 version installed on my test phones.
So you're on stock based InsertCoin ROM ?
As long as it's Android 4.4 KitKat (API Level: 19), it SHOULD parse and install OK.
Click to expand...
Click to collapse
Aha, here might be my problem. My InsertCoin is still the good old JellyBean 4.3 (I am happy with this version and had nearly no problems and all the stuff is working on this one. So if it ain't broke; don't fix it )
The binaries are for ARM devices only (ie 99+% of Android devices). Intel x86 or MIPs can't work (at present.)
I can't think of any other reason it won't parse, unless your copy is corrupted. This is the MD5 I get:
Code:
md5sum ~/Downloads/av-release.apk
2c8328e8cbe1f585f3b1634e36200c8f /home/mike/Downloads/av-release.apk
I'm happy to hear anyone else's stories of success or failure, but I'll need a good 7 hours of sleep first.
Click to expand...
Click to collapse
Got the same MD5: 2C8328E8CBE1F585F3B1634E36200C8F
I am confused or it doesn't work on 4.3
Sleep well!

4.4
Does it work on Android below 4.4?

Can't wait to try it. Your work with Spirit was amazing, so I am sure this is too.

Thanks for the effort, but it ain't working on i9100, cm 11/kk 4.4.2. Tried to increase volume a little (level was about 3, but as you know, first written value is 5), there was a very strange noise as I tried to.increase volume via volume buttons while listening music via headphones. It was a crackling noise, looked to me like the phone is going to get damaged, so I removed HAL and uninstalled your app.

Rinoceros said:
Aha, here might be my problem. My InsertCoin is still the good old JellyBean 4.3 (I am happy with this version and had nearly no problems and all the stuff is working on this one. So if it ain't broke; don't fix it )
Got the same MD5: 2C8328E8CBE1F585F3B1634E36200C8F
I am confused or it doesn't work on 4.3
Sleep well!
Click to expand...
Click to collapse
Here's a v1.0.2 test release that will install on Android 2.2+: http://d-h.st/QfV

Draw Em! said:
Does it work on Android below 4.4?
Click to expand...
Click to collapse
It may. Here's a 2.2+ test release: http://d-h.st/QfV
Chances are lower the lower the Android version. I'd recommend 4.1+, but it may work on some Android 4.0 as well. Android 2.3 GB and older used a "legacy HAL API" which won't work.
At this time it's a "bleading edge" release, and most people comfortable with that have been running 4.4 the last 6 months, I'd think.

pilgrim011 said:
Thanks for the effort, but it ain't working on i9100, cm 11/kk 4.4.2. Tried to increase volume a little (level was about 3, but as you know, first written value is 5), there was a very strange noise as I tried to.increase volume via volume buttons while listening music via headphones. It was a crackling noise, looked to me like the phone is going to get damaged, so I removed HAL and uninstalled your app.
Click to expand...
Click to collapse
It sounds like it was working then, as it does for me on my 9100 with CM11.
In many circumstances audio amplitude will already be maxed out, and trying to increase volume will only result in the automatic gain control kicking in with a different value many times per second, thus leading to distortion and other audio "artifacts".
This solution is more helpful when, for some reason, the audio source material doesn't use the full 16 bits of amplitude. If the VU indicators in the app are showing peaks around 80-90% of the screen width, when the normal volume control is maxed, then amplitude is probably above 16,000 and could be near the absolute peak around 32,000.
For example, some audio may have been recorded that only peaks around 4,000 - 8,000, and for this, and amp factor of 4 may be useful. Another possible solution for this scenario is to enable Compression in DSP Manager or whatever. As with everything, this has pros and cons.
In many circumstances, when possible, it's better to raise analog gain, like Voodoo sound does on the Galaxy S GT-I9000. I'm going to look into this, but this sort of solution is very audio chip dependent.

[Q] Help with ROM choice for Note Pro 12.2

Hi all. I have had my Note Pro 12.2 (wifi version) for about a week now and am planning on rooting/wipe/flash etc this weekend. I'm not sure which ROM would be the best for me, as I don't see much about audio performance mentioned in the custom ROM threads.
I want a ROM that will allow me to do a lot of customization and changing around of settings, but pretty much like stock when I first load it in terms of appearance. I want to be able to get rid of unwanted bloatware (or have it already removed) but i still want to use the pen window and 4-app multi window (but with ability to add any program to the list). Want to add sound on/off setting to the camera (not just replace the sound file with a silent dummy file but actually add the switch to the menu).
I use both the s-pen and a bluetooth mouse frequently and looks like cynogen 12 might not be a good choice because of this, but everyone is raving about the speed and lack of lags. Would be great to get a bit of a performance increase with a new ROM.
But my main concern is audio latency. I'm using Caustic, ntrack, audio evolution etc. Supposedly latency is supposed to be improved again in 5.1 kernel? Not sure if the samsung pro audio sdk is included in any of these ROMs (didn't see anything about that). I'm hoping to try out soundcamp but haven't yet searched for a version of it ported to the note pro.
So are there any good ROMs available which keep the stock functions of the s-pen, bluetooth mouse, multi window, etc, but on a newer kernel with better audio performance? I also use a few of the samsung bundled apps, the hancome office, remote pc, etc. but I want to be able to remove all the bloatware stuff like businessweek, and a lot of the google stuff like music, games, etc.
Any tips on which ROM might be the best for me?

A compilation of issues and missing features for the January 2018 Android 8.0 update

Found at the official MIUI forum:
Xiaomi Mi A1 issues and missing features for Android 8.0 Oreo January 2018 update
I wonder if XDA users have found something else.
Click CONFIRM for the bug reports that you want to be fixed​The issues below are confirmed to be present on all Xiaomi Mi A1 devices for the January 2018 Oreo update.
[NEW] [Android 8.0 January] If the screen is off but the phone is not locked notifications make the screen light up but there are no notifications on the screen! That's a January 2018 regression. Bug report.
[NEW] [Android 8.0 January] SMS text messages backup doesn't work: "Waiting to backup". Bug report.
[NEW] [Android 8.0 December] RCS Phone/Service instead of Android System in battery stats - that's an Oreo regression. Bug report.
[NEW] [Android 8.0 December] Launcher3 bug: icons shape can only be changed if Developer mode is enabled. Bug report.
[NEW] [Android 8.0 December] The phone ignores the Contacts app settings and always uses but doesn't show SIM contacts. Bug report.
White noise for both bluetooth and analogue (3.5mm jack) headphones (slightly improved in the December 2017 update). Discussion. Older discussion. Bug report. Older bug report.
Low light camera performance is horrible for photos and especially for videos due to missing EIS and Camera2API.
High Android System and Android OS power usage/battery drain (reproducible under Oreo as well). Bug report.
Things which Mi A1 users and developers are craving for:
Camera2 API and EIS are not enabled even though both are perfectly supported by software and hardware but disabled only because ... no idea - not to compete with Pixels, I guess. When rooted the solution is to edit build.prop and add persist.camera.eis.enable=1 and set persist.camera.HAL3.enabled=1 ). Bug report.
Add an option to configure display color temperature: there are two very different matrices for MI A1 one of which has a coldish (bluish) hue, another one is warmish (reddish). That also affects how photos and videos are percieved.
Wi-Fi: 40MHz bandwidth for 2.4GHz mode is disabled in software even though hardware is capable. For rooted devices it can be reenabled by editing /data/misc/wifi/WCNSS_qcom_cfg.ini and setting GChannelBondingMode24GHz = 1. Bug report.
The new Google Camera App with HDR+.
There's no option to swap "Back" and "Apps Overview" capacitive buttons. If it's stock Android why it follows Xiaomi's conventions? Bug report.
FM module is present but there's no app for it and it's not exposed to apps (aside from dialling *#*#6484#*#*).
Edit 2018-01-30: The kernel sources for the MI A1 have finally been released - unfortunately they are for Nougat.
Nice to have features:
Gestures: double tap to wake, lift to wake and others which are present in Google Pixels.
Configuring the lighting time of the physical keys.
Making it possible to keep the physical keys always on and configuring their brightness level (also depending on the time of a day).
Bug and feature requests which have been rejected by Xiaomi moderators (what?!):
[Android 8.0] A visual glitch: WiFi/Cellular Indicators have additional dynamic traffic flow symbols which shift the icons to the left of the indicator. Bug report. Here's an app to fix a jumping traffic indicator.
[Android 8.0] "App network access" feature (which allowed to configure per-app WiFi/Cellular access) is no longer present. Bug report.
[Android 8.0] Scheduled power on and off is no longer present. Bug report.
There's a completely unnecessary 1.5GB SWAP partition which causes a tear and wear of the internal storage. Bug report.
These issues need verification:
Some people experience lags and jitters while scrolling, including scrolling in the system settings ( https://youtu.be/wu4CR9tOw8o ). The source of the problem is not known at the moment and the issue doesn't look widespread, i.e. only certain units are affected. Installing the Google Now launcher mostly fixes it.
[Needs root to check] CPU usage monitors cause disk write activity (probably an Android OS bug - need a confirmation from Pixel owners). Discussion. Bug report.
Fixed in the January 2018 update:
[Android 8.0] If you enabled DND mode in volume change UI in Android 7.0(using system UI tuner), in Android 8.0 you will either see empty space or DND icon will be cut off. Bug report.
[Android 8.0] You cannot interact with ambient display notifications. Also if your phone is not locked but the screen is off, you cannot answer an incoming call from the lock screen. Bug report.
[Android 8.0] There's no UI/setting to enable fingerprint swipe notification gesture. Bug report.
[Android 8.0] Under some circumstances the GPS icon might stuck. Bug report.
[Android 8.0] Certain users report that BlueTooth is seemingly draining their batteries. Bug report.
Bad audio for video recording. When rooted the solution is to edit build.prop and set ro.qc.sdk.audio.fluencetype=fluencepro. Bug report.
SIM is "HD Capable" icon..
Erroneous "rapid charging" message.
[Android 8.0 December] Lock screen notifications font doesn't match system settings - it's much bigger. Bug report.
Fixed in the December 2017 update:
Pressing the Home button while being on a second/third/fourth launcher screen doesn't return to the primary home screen. Bug report.
Fingerprint scanner became quite slower with November 2017 update. Bug report.
Complete changelog for updates: three(!) changes for a 1GB update just don't cut it. A better changelog was posted for the December update.
Fixed in the Oreo update:
It's not possible to install the Google Phone app (it does support dual SIM phones). Good bye SPAM protection and caller ID. Why? Bug report.
Xiaomi Mi A1 Contacts app is a different app than Google Contacts for no obvious reasons. Bug report.
Google Assistant sometimes doesn't speak. Discussion. Bug report, another bug report.
The camera app uses a zoom lens instead of a normal lens for recording video. Discussion. Bug report.
Some people report that the fingerprint scanner is still not as snappy as in the October 2017 update. Discussion.
To be updated.

Xiaomi needs to fix all this ASAP! Mi A1 has potential, but it seems like they are undermining the device on purpose.

The OP has been updated.

I agree to every single point you have made. The biggest concern for me is the battery, the difference between the battery backup of Oct and Nov update is almost of 1 hour - 1 hour 30 mins of SOT, which is huge!
Also i like how you have pointed out the dialer and contacts application differences, which is a thing I have wondered from the start. Why the hell not just included Google's own dialer or atleast the contacts application since this whole project is a brainchild of Google itself!? Moreover that contacts application sucks, it shows duplicates for Google and WhatsApp and even Truecaller contacts while calling, so a single contact has 3 duplicates for no damn reason, without any option to sort the same out! The default dialer too doesn't show contact picture for incoming or outgoing calls. I wonder why Xiaomi is hell bent on ruining such an awesome device.

Xadus said:
I agree to every single point you have made. The biggest concern for me is the battery, the difference between the battery backup of Oct and Nov update is almost of 1 hour - 1 hour 30 mins of SOT, which is huge!
Also i like how you have pointed out the dialer and contacts application differences, which is a thing I have wondered from the start. Why the hell not just included Google's own dialer or atleast the contacts application since this whole project is a brainchild of Google itself!? Moreover that contacts application sucks, it shows duplicates for Google and WhatsApp and even Truecaller contacts while calling, so a single contact has 3 duplicates for no damn reason, without any option to sort the same out! The default dialer too doesn't show contact picture for incoming or outgoing calls. I wonder why Xiaomi is hell bent on ruining such an awesome device.
Click to expand...
Click to collapse
If you want it solved and not only to complain, you can fix some of the issues in few minutes. XDA used to be place for mods and tips & tricks, not for whining (MIUI forum is obviously the right place for that).
1. No option to remap "Back" and "Apps Overview" capacitive buttons.
It's not possible even on stock Android. Just install button mapper by flar2 and configure all HW buttons as you wish.
2. No camera2 API and no EIS even though both perfectly supported by software and hardware but disabled only because ...
Install Magisk with appropriate module and modded Gcam.
3. It's not possible to install Google Dialer.
Install Magisk with appropriate module, then install Google dialer from play store.
4. Xiaomi Mi A1 Contacts App is a different app than Google Contacts for no obvious reasons.
Install Google contacts from play store.
5. FM module is present but there's no app for it and it's not exposed to apps (aside from dialling *#*#6484#*#*).
Install Magisk and 3rd party Radio app.
6. Bad audio for video recording.
Install Magisk and appropriate module.

_mysiak_ said:
If you want it solved and not only to complain, you can fix some of the issues in few minutes. XDA used to be place for mods and tips & tricks, not for whining (MIUI forum is obviously the right place for that).
1. No option to remap "Back" and "Apps Overview" capacitive buttons.
It's not possible even on stock Android. Just install button mapper by flar2 and configure all HW buttons as you wish.
2. No camera2 API and no EIS even though both perfectly supported by software and hardware but disabled only because ...
Install Magisk with appropriate module and modded Gcam.
3. It's not possible to install Google Dialer.
Install Magisk with appropriate module, then install Google dialer from play store.
4. Xiaomi Mi A1 Contacts App is a different app than Google Contacts for no obvious reasons.
Install Google contacts from play store.
5. FM module is present but there's no app for it and it's not exposed to apps (aside from dialling *#*#6484#*#*).
Install Magisk and 3rd party Radio app.
6. Bad audio for video recording.
Install Magisk and appropriate module.
Click to expand...
Click to collapse
With all due respect, you may be rich and would not mind spending 15k on a phone to explore "mods and tips & tricks" in it's first 2 months of use and you may even have all the time in the world to spend on XDA and find the "mods and tips & tricks" for every phone you buy off your money; But, there are people who buy the device and expect things to be good after spending a sum of money which may be more/less according to personal preferences and who would not want to unlock and root so soon. Especially more so when the phone is advertised as a Google initiative Android One phone. I have been on XDA long enough and I don't need someone telling what does it stand for and what counts as "whining" and which forum should I go to do it. I am not fond of throwing bread crumbs to every little pesky things that comes in the way; and I am supporting the OP on the thread on points he have made.
Thank you for your time to point out the obvious solutions.
Ah, also, it seems I have run out of bread for you good sir. Good day!

Dialer and Contacts apps are AOSP ones, apparently Android one uses AOSP ones and Google ones are used on Pixels.

Xadus said:
With all due respect, you may be rich and would not mind spending 15k on a phone to explore "mods and tips & tricks" in it's first 2 months of use and you may even have all the time in the world to spend on XDA and find the "mods and tips & tricks" for every phone you buy off your money; But, there are people who buy the device and expect things to be good after spending a sum of money which may be more/less according to personal preferences and who would not want to unlock and root so soon. Especially more so when the phone is advertised as a Google initiative Android One phone. I have been on XDA long enough and I don't need someone telling what does it stand for and what counts as "whining" and which forum should I go to do it. I am not fond of throwing bread crumbs to every little pesky things that comes in the way; and I am supporting the OP on the thread on points he have made.
Thank you for your time to point out the obvious solutions.
Ah, also, it seems I have run out of bread for you good sir. Good day!
Click to expand...
Click to collapse
Yes, I do spend time on XDA before I purchase a phone. If there is a risk that phone will have low interest in XDA community or it's not possible to root it, I simply pass it and buy something else. It's about priorities, few hours at XDA will save me from weeks/months with phone which I don't like. I would advise the same to you, especially if you don't want to root and mod your phone. Better luck next time with choosing your perfect cheap phone.

Xadus said:
With all due respect, you may be rich and would not mind spending 15k on a phone to explore "mods and tips & tricks" in it's first 2 months of use and you may even have all the time in the world to spend on XDA and find the "mods and tips & tricks" for every phone you buy off your money; But, there are people who buy the device and expect things to be good after spending a sum of money which may be more/less according to personal preferences and who would not want to unlock and root so soon. Especially more so when the phone is advertised as a Google initiative Android One phone. I have been on XDA long enough and I don't need someone telling what does it stand for and what counts as "whining" and which forum should I go to do it. I am not fond of throwing bread crumbs to every little pesky things that comes in the way; and I am supporting the OP on the thread on points he have made.
Thank you for your time to point out the obvious solutions.
Ah, also, it seems I have run out of bread for you good sir. Good day!
Click to expand...
Click to collapse
I couldn't say better. I don't want to root and mod my phone right off the bat just because Google and Xiaomi cannot properly collaborate. Maybe three/four years later, when its support has stopped, I will root and mod it to hell, but right now I prefer stock experience and locked bootloader because it gives me a feeling of safety and security. I'm not afraid to do banking on my phone, I'm not afraid to make online purchases. Once the phone is rooted, all the hell breaks loose and I no longer can trust my phone.

MI A1 DETAILED REVIEW AFTER COUPLE OF DAYS OF USAGE.
Pros :
1) Potrait shots are exceptionally well in good light conditions.
2) HDR works pretty well in Daylight.
3) The Dirac Sound built in is fabulous both in terms of speakers & on headphones.
4) Build quality is amazing.
5) Voice quality is very very clear.
Cons:
1) Night mode is really really bad.(Too much noise & Shaky pictures are captured ,loses focus most of the time)
2) Lack of image stabilization while clicking pictures in HDR mode as well as normal mode.
(Slight shaking of phone loses focus in HDR mode and makes pictures blurry)(MUST NEEDED IN NEXT UPDATE)
3) HDR mode in artificial light feels too much exposed over bright light and image feels too artificial.
4) No Electronic image stabilization (EIS) while shooting video its too shaky & not upto the mark.(MUST NEEDED IN NEXT UPDATE)
5) 2X shots are not that great when zoomed even 50% and also are much noisy at times.
6) The UI is smooth but feels at times having less transiston.(Forced swipe has to be done from up to down & from down to up)
7) Selfies are bit artificial at times want it more natural and too much beautification is being applied.
8) In phone app while clearing the call history the app crashes and doesn't clear the call history. It force stops.

Oreo beta testing is worthless at the moment. Beta testers all praise how wonderful it is without mentioning any bugs. Either Re Tardos or just unfit for the job.

I have to say I've been very pleased with the December update. The phone feels much snappier coming from the November update which was a mess with the home button issues. Headphone hissing has also been fixed for me in the December update.

_mysiak_ said:
5. FM module is present but there's no app for it and it's not exposed to apps (aside from dialling *#*#6484#*#*).
Install Magisk and 3rd party Radio app.
Click to expand...
Click to collapse
There is a 3rd party app for radio? Can you give link for this? Thanks.

Is it just me? The hissing noise is much more audible since Dec update. Using Mi In Ear Pro HD. Previously its there but just not that audible. Now its pretty obvious

soralz said:
Is it just me? The hissing noise is much more audible since Dec update. Using Mi In Ear Pro HD. Previously its there but just not that audible. Now its pretty obvious
Click to expand...
Click to collapse
For me it's pretty much the same, didn't notice any improvement or degradation with December update. Still can't use some of my headphones without impedance adapter.

Anyone has any ideas why the photos are 9mp instead of 12mp? It is very frustrating that one fourth of the camera megapixels are deleted somehow.

blackice999 said:
Anyone has any ideas why the photos are 9mp instead of 12mp? It is very frustrating that one fourth of the camera megapixels are deleted somehow.
Click to expand...
Click to collapse
Your camera frame would be 16:9(Full screen), change it to 4:3(standard). And your pics will be 12mp.
https://photos.app.goo.gl/flQfFXBfP0YqizUh2
Visit link if you don't understand

Hey,
thanks for the quick reply, I did change it and now it is ok. I couldn't check the content of the album as it said it is empty,but whatever.

Does sRGB work for anyone? Is it a recognized bug or we will never get proper sRGB colors?

Hello, after december update i have noticed that when i am on mobile data i can't download any apps from google play. I tried different solutios(hard reset, clear cache, clear data, blabla) and nothing really works. Do some of you experience that?

Question Seeking Custom ROM Recommendations with Auto-Answer Feature for Calls

Is there a custom ROM available that includes an auto-answer feature for incoming calls? I've been using MIUI, but it doesn't always answer calls automatically despite enabling the 'always' option and the option for automatic answering with headphones. I recently tried Evolution X, which I like for its lightweight nature, but it doesn't have the auto-answer feature. Can anyone recommend a ROM with this functionality? Additionally, I'm curious to know if every Pixel ROM includes the auto-answer feature or if there are specific ROMs that offer it. I really need this feature, please help

Would you really need a custom ROM for that?
Can't you just use a different caller app that includes this feature?

Haldi4803 said:
Would you really need a custom ROM for that?
Can't you just use a different caller app that includes this feature?
Click to expand...
Click to collapse
i have already tried using different caller apps like MotoAnswer, but they have limitations such as restricting the number of calls that can be automatically answered in a day. (It is not enough for me because sometimes the call is closed by mistake. understand what I mean)

yukinoshita said:
i have already tried using different caller apps like MotoAnswer, but they have limitations such as restricting the number of calls that can be automatically answered in a day. (It is not enough for me because sometimes the call is closed by mistake. understand what I mean)
Click to expand...
Click to collapse
you should be looking for apps that don't have that limitation instead, this is not a ROM side thing I think. have you tried Truecaller Assistant?