yashsingh1/xdaforums huggingface dataset:
[Nexus 5 Original Android Development] Splder:
nice fixed the audio bug

short replay:

edit: /system/etc/audio_policy.conf

and delete red text from line:

flags AUDIO_OUTPUT_FLAG_FAST|AUDIO_OUTPUT_FLAG_PRIMARY|AUDIO_OUTPUT_FLAG_RAW

reboot and audio bug is fixed

long replay:

oh yesterday i never looked at what was changed on github did not relise it was just the audio_policy.conf and mixer_paths.xml files

link to change: https://github.com/CyanogenMod/andr...mmit/67cebdefc36458aa3922e41b247cadddb6a9ce4f

OK so i fixed it

flashed 20/7/2016

tested average Db = 49

edit /system/etc/audio_policy.conf deleted red text

flags AUDIO_OUTPUT_FLAG_FAST|AUDIO_OUTPUT_FLAG_PRIMARY|AUDIO_OUTPUT_FLAG_RAW

reboot

tested average Db = 59

FIXED!!!! :)

I never touched the mixer_paths.xml i'm not sure if the mixer_paths.xml edit can work independent of the audio_policy.conf edit or if the mixer_path now just has dead code?
[Nexus 5 Original Android Development] HermannSenator:
Thank You! Now the sound's working pretty well! :D
[Nexus 5 Original Android Development] RancidPenguins:
Clean install of today's nightly from myfluxi makes the setup wizard unusable. Clicking 'next' just causes a strange interaction with the status bar, where it is partially visible as well as a lock icon, similar to when Cyanogenmod had a general issue with Live Lock Screen with a lot of devices.

Tested multiple times with Pico Gapps from OpenGapps, although it works fine without Gapps.
[Nexus 5 Original Android Development] realdoctortim:
I'm getting the same problem. Using the 20160722 nightly with microgapps. Clicking next (to select country) the status bar pops down briefly but no press is registered in the interface. Rebooting helped me get past the country select but I got stuck trying to enter the password for my wifi.
[Nexus 5 Original Android Development] RancidPenguins:
I had the same idea. I ended up flashing the build from the 19th, setting up and then dirty flashing the latest build. No problems so far.
[Nexus 5 Original Android Development] mmo.xda:
It seems an issue with the general source.

This commit (https://review.cyanogenmod.org/#/c/150974) maybe the culprit.

Regards
[Nexus 5 Original Android Development] elitewarrior:
[MENTION=4152171]myfluxi[/MENTION]

Regarding the sound issues... they exist: https://productforums.google.com/forum/#!topic/nexus/aAzHDStBDQU

This apparently fixes them: https://github.com/flar2/ElementalX-N5/commit/7d617ccdb0590df85f53199d80afd8ff00050731

Sourced from: https://plus.google.com/u/0/+FranciscoFranco1990/posts/KuA2xHz4XUS

Edit: Was just trying to help. Not sure if this is already merged for our builds or not. Not really too knowledgeable regarding this stuff.
[Nexus 5 Original Android Development] kenshin33:
that line is already there (hammerheadcaf), git blame shows that it was intruduced with the folowing commit :

commit 6eb6d1817c8be8eecda0dbb096c58100a36a44af
Author: Gopikrishnaiah Anandan <agopik@codeaurora.org>
Date: Fri Aug 16 17:34:21 2013 -0400

Soc: msm: qdsp6v2: Fix invalid params handling

Alloc and free apis should sanity check all input params.
If allocation fails set client and ion handle to NULL.

Change-Id: Ide3bd782eb90ee8b033e39de232929a1ca7174b7
Signed-off-by: Gopikrishnaiah Anandan <agopik@codeaurora.org>

https://github.com/CyanogenMod/andr...mmit/6eb6d1817c8be8eecda0dbb096c58100a36a44af
[Nexus 5 Original Android Development] :
[MENTION=4478126]elitewarrior[/MENTION]

That's our source file: https://github.com/CyanogenMod/andr...caf/arch/arm/mach-msm/qdsp6v2/msm_audio_ion.c

Now go and compare the msm_audio_ion_import.

EDIT: Thanks kenshin33, didn't notice your comment!
[Nexus 5 Original Android Development] myfluxi:
I suggested this change to test to [MENTION=2216940]mmo.xda[/MENTION] some days ago via email. The HAL picks the ULL usecase which was a bit surprising but I still cannot reproduce the behavior where notifications were "only one third" as loud as before. It's all fine for me, still. I'll remove the RAW flag, though.

This might be my last contribution to CM, I don't know what really happend over there since I intentionally stayed away from CM since last year. It does not sound good but it fits a certain scheme that I grew to hate. I see all those sarcastic and malicious comments to the news, people even take CM people in hostage for cyngn's crap. A lot of comments show, how rotten certain users are, complaining about volunteer work. I really don't know, what to do. Then I look at our gerrit and sometimes it makes me shiver, I cannot stand certain people and I cannot stand what they do. Also I think, cyngn people get involved in a way they shouldn't. Instead of fixing their commercial devices, they **** around in the OSS branch. Bottom line: It's not worth it, Android only makes me sad. I ride my bike again, I win races, I'm in tip top shape, it gives me satisfaction. I have no time for negative things in my life, I have no time for other people's problems.
[Nexus 5 Original Android Development] mmo.xda:
That is true! [MENTION=4152171]myfluxi[/MENTION] was on the right way on Friday. He made me several questions and told me to test that on Friday morning. But I'm afraid I could only answer him to his questions but I was not able to test it. I had more than 45 work calls that Friday :( :(

Later, on Saturday I read that someone post that...and the rest is history.

Anyway, thanks [MENTION=4152171]myfluxi[/MENTION] for look into this. Thanks again.

About this, news coming from Seattle are very strange.

On the other hand, you have done such great things to hammerhead and open source, so, again, the only thing we can say is thanks for your time and effort.

Whatever you are going to do, please enjoy and take care.

Regards
[Nexus 5 Original Android Development] Cristiano Matos:
Wise choice man. I don't have the same skills that you have but in the past i was messing around with android codes (java) and keeping a custom rom. My dead line was some people are stupid. Some are here just to make other people lives worst. Now i only run (love to do it). Keep biking and be happy. Thanks for all your contribution so far.
[Nexus 5 Original Android Development] Splder:
Developing roms is very time consuming and you get pretty much nothing in return

So im always astounding at how much time developers put into working on roms

I my self enjoy developing apps as i work on my own i have full control of the project and developing a app is no where near as hard as developing a rom so it can easily be done by one person and you can also make a bit of money on the side

I also ride but i ride a Yamaha WR250R but iv got some back problems so been stuck at home for the past 2 months going to take a mri scan today see how messed up i am
[Nexus 5 Original Android Development] :
Very sad to hear that! I can comprehend your decision. I don't want to sound too trumpish, but you made the Nexus 5 great again!

Get well soon, Splder!
[Nexus 5 Original Android Development] :
Guys, quick question: There's an option under Settings which turns on the camera as soon as you double-tap the power button. Does it work for you? My camera doesn't connect. Opening via app works fine though...

Thanks in advance!
[Nexus 5 Original Android Development] djalfy:
Works fine for me.
[Nexus 5 Original Android Development] :
Thank you! May I ask which nightly you've got installed? :)
[Nexus 5 Original Android Development] nexzor:
ahh was wondering why sometimes my camera pops up when i aktivate the device. i´m on 20160621 Myfluxi build
[Nexus 5 Original Android Development] joshuas_79:
works fine here. 20160726 nightly

Edit: sorry , I thought I was in non-CAF version thread. XD. I'm using stock CM13 nonCAF
[Nexus 5 Original Android Development] djalfy:
20160630. Will test today on latest nightly as i plan to give it a try and see if i experience that sound bug everyone's talking about
[Nexus 5 Original Android Development] bejunk:
Make sure you make your camera the default one, like opening it via whatsapp and select as default. Then it should work. Also AFAIK, you can unlock normally after double press & it asks you?!

Peace ✌
[Nexus 5 Original Android Development] CataHd:
do i need a specific bootloader and radio to install this?
[Nexus 5 Original Android Development] alturismo:
Check Topic
[Nexus 5 Original Android Development] JulianXhokaxhiu:
Can someone please tell me if when installing the Google Camera app, the HDR+ option is available? Last time on 12.1 CAF this was not working ( because of hammerheadcaf name on build.prop that Camera app was checking ).

Thanks in advace for any answer given.
[Nexus 5 Original Android Development] EnginEAR:
HDR+

It works!
[Nexus 5 Original Android Development] EnginEAR:
SetupWizard

SetupWizard is still **** on November 15th, 2015... Just so you guys know...

---------- Post added at 09:58 AM ---------- Previous post was at 09:36 AM ----------

Root isn't working for me on November 15th build...

---------- Post added at 10:15 AM ---------- Previous post was at 09:58 AM ----------

Reverted to November 11th build... :crying:
[Nexus 5 Original Android Development] richj85:
I may be going mad, but I hadn't seen the build for the 15th on the forum?
[Nexus 5 Original Android Development] EnginEAR:
It's not explicitly on the forum; however, you can find it here: https://www.androidfilehost.com/?w=files&flid=41992

And the original post does refer to myfluxi's androidfilehost...
[Nexus 5 Original Android Development] banciii:
U sure about it?

And opengapps pico working without any issue since 9 november. Try the pico package.

Tapatalk-kal küldve az én Nexus 5 CAF-el
[Nexus 5 Original Android Development] EnginEAR:
It seemed like it was working but some specifics were not...

I use the nano opengapps from November 15th...
[Nexus 5 Original Android Development] banciii:
Then u have some kind of weird unique issue. I have greenify, mixplorer, cm file explorer, catlog, root explorer, titanium backup, xposed, and every apps' root functions working well, just as gapps.

Tapatalk-kal küldve az én Nexus 5 CAF-el
[Nexus 5 Original Android Development] EnginEAR:
On the November 15th build?

Do you use SuperSu? if so - which version?
[Nexus 5 Original Android Development] myfluxi:
Sure and it always worked unless crazy people do crazy things to create crazy problems that should not exist in the first place.
[Nexus 5 Original Android Development] banciii:
Yes, latest nov15 build with nov15 opengapps-pico. And no, I don't use supersu, I m usin the cm su.

Tapatalk-kal küldve az én Nexus 5 CAF-el
[Nexus 5 Original Android Development] Sly_67:
Why can't I install supersu binarys? Is it supersu fault? I have root access but without supersu Titanium backup isn't working like I expect to. Can't change android ID number from backup.

I like CM13 CAF, but I need TB to install my apps+data.
[Nexus 5 Original Android Development] EnginEAR:
I didn't say I can't install SuperSU. It is installed.

TitaniumBackup seems to work well. FauxSound as well.

RootExplorer and Synapse don't actually do what they are supposed to...

2 out of 4 in my case... I don't use other apps with root access...

---------- Post added at 01:23 PM ---------- Previous post was at 01:10 PM ----------

Looks like even Synapse managed to work after all...

Am only missing RootExplorer... I always change the ro.sf.lcd_density to 360 in /system/build.prop and now it fails to change this file...

Too bad...

Everything else might be working fine... I just don't know...
[Nexus 5 Original Android Development] mmo.xda:
AdAway does NOT work. It can not write to host file.

It seems a fault on root access claim.

I will revert to 11/11 build.

Regards
[Nexus 5 Original Android Development] banciii:
Just checked Root Explorer with your desired modification and I also couldn't do it. I can switch to R/W but it looks like it's fake, I can't modify build.prop. Donno if it's an su or a root explorer incompatibility issue. Update: Yeah, probably it's an su bug, since cm file manager also can't execute root actions. :(
[Nexus 5 Original Android Development] EnginEAR:
The Dude

I'm not wrong... I'm just an asshole...
[Nexus 5 Original Android Development] JulianXhokaxhiu:
Thank you for the proof sir. Although I don't understand who your're referring to, I may only say that I tried CM CAF from Cyanogenmod official website and there it was not really working. That's why I was asking. Then I'm glad to proceed on testing your ROM which sounds really interesting to me :)

Thank you for all the effort put back in this project! ( I was there when you decide to leave the community, a really sad news that time, but I'm really happy you're back )

Cheers!

Thanks to you also :)
[Nexus 5 Original Android Development] scrack26:
Did you flash SuperSU? Because I am on Build dated Nov 11. And i can change my DPI on Root Explorer. Just using the cm root on developer options didn't flash any another kernel or supersu.
[Nexus 5 Original Android Development] :
Yeah, I'm going to do a clean install anyways because yesterday I screwed it all up while tinkering with system files... :D
[Nexus 5 Original Android Development] razorloves:
I've been looking into that gello issue.

I noticed a few weeks ago that the gello builds that are built once a week were not being updated.

The cm jenkins build server was just spitting out the same exact gello apk every time.

And it's been doing that for around 7 weeks, so the last like 12 or 13 changes to gello were not in the gello apk in the nightlies.

So i discussed the issue with the cm jenkins administrator yesterday (zifnab), and he discovered the gello builds were actually failing and he fixed the issue.

Now, gello is finally fixed and updated in the 30 july nightly.

No more ask_es crash for spanish (españa).

And no more yandex_ru crash for russian.

:good:
[Nexus 5 Original Android Development] djalfy:
I've tested this on a clean install anf it still works. But i've noticed something weird. Before flashing the latest nightly i formatted the data and cache partitions in f2fs and then flashed all the zips i allways use (cm, open gapps aroma, xposed framework, cm actions, busybox, etc.) After the first boot everything worked fine. I installed xposed installer material design and the xposed modules i allways use (lucky patcher, gravity box, minmin guard, android n-ify, greenify and amplify battery extender) and activated them and then i rebooted. After the first reboot i noticed that gravity box wasn't doing anything(no ui elements were change as i've set them up like the custom power menu items, signal cluster settings, etc. Lucky patcher wasn't working at all, minmin guard wasn't blocking any ads and the list goes on. I tried rebooting again and after that reboot most of the apps i've installed on my phone were gone, including some of the google apps i've installed with the aroma open gapps package and i kept getting the message "com.android.media process has crashed". I've checked the xposed logs and everything looked normal. No error message at all. Then i've rebooted into recovery and noticed in the twrp logs 3 or 4 lines saying something like "data/data/com.dropbox could not be opened as the folder does not exist". I've then formatted the data partition to ext4 and reflashed everything again and everything worked fine. All xposed modules worked fine since the first reboot and i did plenty of reboots since then and no app disappeared/stopped working. Does anyone else have the data and cache partitions formated to f2fs and experience these problems? Sorry for not providing any logs but when i did this it was like 4 AM and i was too tired to capture the logs. I just wanted to make the phone work again and go to sleep asap. If anyone needs some logs i am willing to test this again under the same conditions in the next few days when i hafe some spare time. Sorry for the long post and bad english. Thank you!
[Nexus 5 Original Android Development] A Chinese XDA user:
I had these two partitions formatted as f2fs several weeks ago, and one time I reboot to install update I got error messages in twrp that some file in /data was corrupted and when the update is complete, I am stuck in a bootloop, i had to factory reset to boot back up. Since then I stayed away from f2fs.
[Nexus 5 Original Android Development] mmo.xda:
Oh great! Thanks for your efforts!

I will repo sync and build myself ASAP.

Kind regards and thanks again

P.D.- I can confirm that Gello settings are now working in spanish locale.

Thanks everybody for your efforts in this way
[Nexus 5 Original Android Development] ghostrider08:
Just a heads up if anyone is running an older version and plans to upgrade.

I was a bit out of the loop -- had a 18022016 nightly with the HH12K bootloader. I've updated the bootloader to HHZ20g (found here https://nyyu.tk/cm13/ under the "Nexus 5 - hammerheadcaf" header) and dirty flashed the latest nightly (31072016). Everything works as far as I can tell.

Thanks to the developers for not abandoning this release! Cheers!
[Nexus 5 Original Android Development] Allen_Walker:
Anybody knows what is version f2fs driver in last nightly?

Last version working good (stable, not lost data storage) but I want not to install custom kernel. ;)

https://kernel.googlesource.com/pub/scm/linux/kernel/git/jaegeuk/f2fs/
[Nexus 5 Original Android Development] just_kip:
Is it possible to enable battery saving mode manually? Button from quick settings does not work.
[Nexus 5 Original Android Development] :
It does work for me.

You can manually enable it under Settings -> battery :)
[Nexus 5 Original Android Development] just_kip:
I have not such option
[Nexus 5 Original Android Development] Allen_Walker:
It's for Caf build only.
[Nexus 5 Original Android Development] ninja_rancher:
Tried to determine from the discussion in this thread and the non-CAF one if the volume issue had been addressed, but couldn't find a definitive "yes" or "no". Are things back to normal with the latest nightlies? Thanks.
[Nexus 5 Original Android Development] :
Yes, previous issue has been fixed. :)
[Nexus 5 Original Android Development] morphvale:
Anyone else having issues booting up after yesterday's commits?

Tried building both last night and just now, all I get is the Google boot logo and nothing happens from there.
[Nexus 5 Original Android Development] :
Yesterday, there was a commit which broke the actual build process. It was fixed pretty fast. However, the actual output product should be fine. I built my own daily update right now and it's booting up fine :)
[Nexus 5 Original Android Development] morphvale:
Thank you for the info, but the build is fine. Build time is the same (around 1:45 on my computer for a clean build) but after installing (tried both a clean and a dirty flash) I just get stuck at the logo. Only thing I'm currently cherry picking extra is fast charge, and another commit to change the path to the kernel folder to hammerheadcaf, instead of hammerhead, but I guess it can't be those.

I was cherry-picking the blur stuff before, but looks like those got merged.
[Nexus 5 Original Android Development] :
Hm, that's strange. Can you link me to that specific cherry-picks? And yes, the blur stuff got merged - no need to cherry-pick it any further :)
[Nexus 5 Original Android Development] myfluxi:
Our CM githubs exploded, we have all the bells and whistles and are awesome again.
[Nexus 5 Original Android Development] amnher:
Two of the devs have already stated that M is the end of the road of the respective custom rom. Our hope is CM for android 7.0

by the way does caf have some issue regarding lowered performance after battery saving is on/off??
[Nexus 5 Original Android Development] morphvale:
Nevermind, there might have been something wrong with my build tree. I manually removed frameworks, device, kernel and vendor trees, cherry-picked the new kernel and device commits from myfluxi that still haven't been merged yet, and did another build. That booted just fine.

But anyway, just if anyone needs them, here they are:

Main fast charge: https://github.com/AICP/kernel_lge_hammerhead/commit/6766adc1b9dc124fd6fad54598a92e234f57358c

Set fast charge to 1,2A: https://github.com/AICP/kernel_lge_hammerhead/commit/b284a9f0bfc6d39cc6b712f829681cc5b5228a78

Reset kernel path to kernel/lge/hammerheadcaf: http://review.cyanogenmod.org/#/c/131703/
[Nexus 5 Original Android Development] just_kip:
On CAF power save works without this issue
[Nexus 5 Original Android Development] myfluxi:
I don't think, fast charging mods are allowed on CM devices. With the inofficial status of hhcaf we're somehow in a grey area but still. Regarding that implementation...a million horrible lines of code, a zillion sysfs knobs for very, very trivial things as always just to sell a control app in the play store. I'll look at this.
[Nexus 5 Original Android Development] myfluxi:
I updated to the latest which I will continue to do. And yes, it's a good decision to use what is on CMs github.
[Nexus 5 Original Android Development] myfluxi:
If our M blobbage works in N, there is no reason why we wouldn't be able to have a great Nougat experience as well.
[Nexus 5 Original Android Development] morphvale:
Never found an answer for why this hasn't been added to CM. However, for trivial reasons, I rarely use a wall charger for my N5. Usually it's either connected to a laptop, or my wireless charger overnight. I kind of found it necessary, and that was one of the solutions I found online. I've been using it for maybe close to one year and didn't notice any issues so far. Can't say it's the right way to do it, my C skills are quite low, especially when it's for Android.
[Nexus 5 Original Android Development] amnher:
otherwise if not? so a bringup must be done?
[Nexus 5 Original Android Development] eternal70:
Any chance for aosp-caf branch in the future alobgside with cm-caf? I thought we will depend on CAF in the future because Google will no longer update our device tree
[Nexus 5 Original Android Development] myfluxi:
???

We will borrow changes M -> N from shamu (as it is very close in in architecture and also pretty old), other Nexii and CAFs device trees, just like any other OEM, device. CAF borrows changes from AOSP. AOSP ist the master, everything derives from there, everything ist applied on top of AOSP. On the other hand AOSPs HALSs derive from CAF. CM will probably update the OPO and ZUK so we can borrow a blob or two from there as well. Then we need some hackery around possible changes inside future N blobs - just like any other device without Android major release support. 8974 will be able to run N for sure.
[Nexus 5 Original Android Development] myfluxi:
Regarding fast charging, this stuff is not allowed in CM. On the other hand, in these days with USB 3.0 it should be pretty safe to pull up to 900mA over USB. And capable chargers will provide more than 1200mA easily. The kernel charger driver limits input at 3A, the hardware is capable of 4.5A. I played with it a bit yesterday, the maximum I was able to pull over a PC USB 3.0 port was ~700mA, wireless pulls 700mA as well (as advertised).

Regarding the implementation of "Fast charge kernel modules", existing modules are so emberrassing. Basically you need one line to patch it, you need 3 lines if you want a userspace toggle. With a handful of lines more you make it fully configurable. WTH did these kids write hundreds of lines of crap??

It should be easy to export the actual charging current (and also real time consumption) from kernel space so the logic is not in some app that watches battery mV delta and divides by time. It's all there and can be exposed with just a few lines of code.
[Nexus 5 Original Android Development] Dark_Eyes_:
It's so good to have you back [MENTION=4152171]myfluxi[/MENTION]. You're on fire, are you? Great timing, N is coming ;)
[Nexus 5 Original Android Development] rogers11:
Hello, is it necessary to press the Power button twice sometimes to get the screen on again after the other side has ended a call?

I had this problem with non-CAF some time ago and switched to another ROM. Now I'm thinking about going to CAF.

Thanks in advance.