yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] kemihansome:
Frankly speaking I just said yes to every pm that asked to include it. Wasn't really uptight about it lol. So I'm not sure who's added it as long as the team gets credited :)

Lol.... That's nice of you,

All the same I love your work,

Keep it going :D
[Samsung Galaxy Nexus] Sparx639:
Its mostly stuff from YouTube and Pandora, but I'll try to put a list together
[Samsung Galaxy Nexus] osm0sis:
Haha you should be afraid of me having free time... ;)

http://xdaforums.com/showthread.php?p=42902217#post42902217
[Samsung Galaxy Nexus] Misledz:
Btw in the latest build I added all the changes you sent by pm already /no1
[Samsung Galaxy Nexus] osm0sis:
I saw! I take it that it works fine then? That's awesome! You just missed deleting the instchk.sh file from /auto since it's not needed for the check anymore. :D

I'm mostly wondering about "libbeatsbass.so and libsrsfx.so are in both /system/lib/ and /system/lib/soundfx/ (neither present in stock, either would make sense)"

/lib also has libbeatscorehtc.so, so libbeatsbass.so might belong more there, but libsrsfx.so could really belong in either spot since /lib has libsrscorehtc.so and libsrsprocessing.so, and /lib/soundfx has libsrscore.so and libsrstb.so.

I've already got all the other stuff I mentioned hacked out of the zip I downloaded. ;)
[Samsung Galaxy Nexus] Misledz:
FUUUUUUUU it makes sense now. I had used windows 8 and their drag and drop function is weird. I was wondering why the n4 build was smaller than the Gnexus. I had it run and tested and it worked fine. On the other hand reverting removes the sound of the n4 again. I'm not sure what's going on...
[Samsung Galaxy Nexus] osm0sis:
That'll probably be the system files that are in delete-list which shouldn't be. :cowboy:

So where SHOULD libsrsfx and libbeatsbass be?
[Samsung Galaxy Nexus] Misledz:
It should have been in the rename, lib folder. I had a test folder in which I placed in soundfx to test if it actually ran from that location but it didn't. It's supposed to be in the lib root folder. When i dragged and dropped it asked to replace, I didn't know it copied the folder too. Fml.
[Samsung Galaxy Nexus] osm0sis:
If it's lib, then it should be delete-list lib. Neither of those two exist on stock. :good:

But do you mean for both beatsbass and srsfx? srsfx looks like it could really go in either since there are other srs libs in each.

Are you glad to have your proof-reader/zip tester back? :laugh:

You were right about the nostalgia. ;)
[Samsung Galaxy Nexus] Misledz:
I missed you script kitty *soft patting*
[Samsung Galaxy Nexus] osm0sis:
Where should srsfx be? :p

I'm itching to flash this sh*t.
[Samsung Galaxy Nexus] Misledz:
Same as lib folder. Although some tend to keep it in soundfx I'm not sure why. Just cause it's fx doesn't mean it should go in soundfx. I haven't really found it overlapping tbh.

DAVECHAPELLE
[Samsung Galaxy Nexus] osm0sis:
Thanks big guy! So /system/lib/soundfx/libsrsfx.so should be in /system/lib, what about:

/system/lib/soundfx/libsrscore.so

/system/lib/soundfx/libsrstb.so

?

You know me, I don't flash anything unless I know it's clean and reversible.
[Samsung Galaxy Nexus] Misledz:
Same as follows buddy, lib folder :P I had to test it first hand and the damned copy paste. I'm pretty sure there is a standard list for soundfx files
[Samsung Galaxy Nexus] Misledz:
Glad it works out the way you want it to bud :)
[Samsung Galaxy Nexus] ali magdy:
Is there a Zip for MIUI 4.1?

Thanks

Sent from a neXus
[Samsung Galaxy Nexus] Misledz:
Why not try the beta 3?
[Samsung Galaxy Nexus] cannibalcollier:
I installed beta 3 on aokp jb nightly and it boost the volume. I use volume+ to set the eq but doesn't always stick. Is anyone else having this issue and is there a way to fix it?
[Samsung Galaxy Nexus] hazimjaved:
working great on jb miui :) thanks man :thumbup:

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] Gucci.Nexus:
Will the mod work if I flash the low latency mod as well?
[Samsung Galaxy Nexus] Misledz:
Just flash the non latency beta, since the latency is under works. And let me know how it fares with you on audio loudness
[Samsung Galaxy Nexus] ali magdy:
Sorry man that question was asked before but you answered it :) . You are doing a great job. Thank you.

Sent from a neXus
[Samsung Galaxy Nexus] privy:
So I flashed v3beta3 and after that I lost all my ringtones and notification sounds..how can I get them back. Sorry if this asked already. Searched and couldn't find anything on it.

Sent from my paranoid nexus
[Samsung Galaxy Nexus] Misledz:
That normally shouldn't happen. Infact it should never happen. That's so weird. Anyways you can get them back via theme section. Galaxy S3 media pack has all the notification sounds and ringtones of the Nexus. Nothing special but they have some sweet add ins. Just copy the notification and ringtones folder to your phone root folder and the phone should pick it up automatically.

Check in system with any root explorer if you have your sounds in system/Media.

Ps: this mod does nothing to affect any of the other system folders. You probably flashed it using ROM Manager or something
[Samsung Galaxy Nexus] :
Restoring the Backup should help

Gesendet von meinem Galaxy Nexus mit Tapatalk 2
[Samsung Galaxy Nexus] Misledz:
Then the mod goes
[Samsung Galaxy Nexus] :
but the sounds will worke again and you can try to flash again

Gesendet von meinem Galaxy Nexus mit Tapatalk 2
[Samsung Galaxy Nexus] cor_mann:
Is this mod via DSP?

Hello,

I have a question about the mod. I checked through the thread but didn't find an answer. I sincerely apologize though if it has already been asked and answered.

Does this mod work via DSP, or does it work at the kernel/firmware level?

I ask because I consider myself an audiophile (whatever that really is) and try to avoid artificial sound enhancements - like Beats Audio, etc.
[Samsung Galaxy Nexus] grognaz:
maybe its the same .nomedia problem?
[Samsung Galaxy Nexus] privy:
So I flashed the revert and reflashed the beta and now I see all the tones. Could be the .nomedia problem or something because I did have the problem and think I fixed it but now I have the mediaservicescanner killing my battery soooo not too sure. I'm gonna do a full wipe and flash everything and see.

Sent from my paranoid nexus
[Samsung Galaxy Nexus] Skilover:
I'm using this with Liquid Beta 2, basically an AOSP Rom (Toro), plus Imoyosen's Lean Kernel (current version 4.3.0 Exp1), and when I try to use the Sound/Music Effects settings, Settings crashes. I'm able to run the DSP app, but cannot change the Music Effects settings as it crashes every time. Ideas?
[Samsung Galaxy Nexus] Zehlek:
Will this work on jb miui based ROMs?
[Samsung Galaxy Nexus] lparcshinoda:
Yes, this was asked SO many times in the previous few posts ;)
[Samsung Galaxy Nexus] Misledz:
well basically DSP was supposed to work but as per the latest JB builds it lacks support. And so it remains there untouched only because the presets work but don't get loaded because of the lack of an update for the DSP, however the loudness does not depend on this factor and will still be as loud, DSP was just there to control the way you hear your music.

but my files don't include any nomedia? :confused:

Yes it will. Just flash the beta3,and it will work as proven a few posts by someone who asked the same question.

perhaps is the media scanning. Sometimes it gets interrupted and you'll need a restart to fix it. Normally when I flash a new firmware I still have the custom tones in a separate folder but only after a restart will it pick it up.

Are you using the beta3 version or the v1?
[Samsung Galaxy Nexus] osm0sis:
Perfect. Alright, manually corrected my zip. If you want to PM me the Louder Farm for the GN I can make all those changes and send it back in an hour. :cowboy: :good:
[Samsung Galaxy Nexus] Misledz:
Please do and I'll call it a night :> it's like 2am and wanted to make sure you enjoyed this one (y)
[Samsung Galaxy Nexus] osm0sis:
Fire away! :D

Flashing my fixed zip now. 3pm here. :p

If you want to send me the Farm for the N4 too I can extract the Google stock system.img and compare to try and figure out what the issue is there. :good:

---------- Post added at 03:34 PM ---------- Previous post was at 03:15 PM ----------

Just got a text notification. It seems a bit on the "crazy loud" side at max volume on the built-in speakers. That's at default post-install settings, so I'll have to try to bring it down a bit with one of the bundled apps and report back. :highfive:

Send me those Farm zips any time.
[Samsung Galaxy Nexus] osm0sis:
You must have been sleepy! You never sent them to me. :p
[Samsung Galaxy Nexus] Misledz:
It's 6am! And yeah I'll be heading out in a bit! I'll send them today :P I finish around 12 got about an hour vacant till work so I'll send it by then buddy! Insane timing btw. I just got up.
[Samsung Galaxy Nexus] osm0sis:
As far as I can tell none of the bundled apps are able to make the notifications any quieter. :( Any way to reduce the volume of the built-in speaker just a bit, while keeping the headphone loudness everyone seems very happy with right now? :cowboy:
[Samsung Galaxy Nexus] jesssiii:
Crazy loud main speaker =GOOD:D

Can't people just turn down their own notification volume?

Toro GNex
[Samsung Galaxy Nexus] Misledz:
You can always try flashing the stock libs from 4.2.2 and replace the libs in the lib folder (except soundfx) believe me when I say it's crazy as to how some people deem it as 'too low', if you searched previously some people keep saying it's still too low /smh/. Crazy! I've come to ignore those posts btw.
[Samsung Galaxy Nexus] osm0sis:
No. Because the way this mod works, ALL the extra volume is on the highest slot; so if you turn it down by one you're turning it down to pre-mod levels minus one. :rolleyes:
[Samsung Galaxy Nexus] Misledz:
I tried fixing that problem on the last 2 versions and that caused it go haywire. People complained the volume wasn't going down anymore, even at 1/15 steps it would still be on max. I removed the volume.db just so that it stays safe.
[Samsung Galaxy Nexus] osm0sis:
Volume.db is still there. :confused:
[Samsung Galaxy Nexus] Misledz:
Huh I had it removed

That's from the zip. Anyways you can delete it from the etc folder it's safe as I found a separate work around with the audio_hw.c version
[Samsung Galaxy Nexus] osm0sis:
It's still there in the latest GN zip anyway. Is that audio_hw.c fix already in V7b4?
[Samsung Galaxy Nexus] Misledz:
Yeah I added it already that's why it's a bit better now compared to before
[Samsung Galaxy Nexus] :
I recently switched from Paranoid Android to MiUI and I was wondering if this mod will work with MiUI. I have a modified version of Franco kernel.
[Samsung Galaxy Nexus] Misledz:
If anything, it should work :)
[Samsung Galaxy Nexus] osm0sis:
Cool, fire me over those Farms. I'll get all these fixes synced up. :cool:

---------- Post added at 02:40 PM ---------- Previous post was at 02:26 PM ----------

Also, can AwesomeBeats.apk function as a user (/data) app or does it need to be in /system?

Edit: Good news. Removing Volume.db seems to have mostly helped my "holy f*ck that's a loud notification" issue. ;)
[Samsung Galaxy Nexus] osm0sis:
I primarily use my phone for music with the built-in speaker, maybe with a nice round bowl for a parabolic amplifier. ;) Then sometimes the headphone jack for Aux In when I'm in my car. For the car, I throw on the High Perf kernel tweak (otherwise I leave it off since it's headphones only and can cause non-headphone bugs). I was also using the kernel Headphone Volume Boost to 1 (since higher also brings out bugs) but I probably won't need to do that anymore with the mod doing the heavy lifting there. :)

I decided to can AwesomeBeats, and use Noozxoide again since I like the way its EQ responds and it works system-wide. Like many have posted, none of the settings except the EQ and the Compression seem to do anything, and the compression sometimes seems to get reversed(?) where turning it off and on starts out one way but then later it seems to switch and the opposite occurs. Best to leave it off I think. It's a shame the app is so buggy.

For my EQ I mostly want to taper the high end which can crackle in the sh*tty GN speaker, especially with some of the indie rock I listen to, so from left to right I run:

+4.0, -3.0, -1.5, -4.5, -3.0 :good:

Since on my speaker the boost makes things too loud, I also have all the system volumes lowered by one notch to avoid clipping.

Line-out for the car I also leave everything disabled except for the EQ and I currently use the Gaming (PSYC) (VSUR) preset since it has some nice volume boost to it.
[Samsung Galaxy Nexus] Misledz:
I like how you experiment with alot of things. Honestly I tend to keep it where I go crazy when listening on the road, but since I drive a motorbike, I can't dance or headbang :crying:
[Samsung Galaxy Nexus] osm0sis:
Haha well car dancing isn't all it's cracked up to be. :p

I'm still tinkering with those as I come across songs that give a bit of buzz, etc.; Just listened to one with an amazing little string section backing up the band, Hey Rosetta!, and had to adjust. You can link that post in the OP if you like. :)
[Samsung Galaxy Nexus] Misledz:
Done, linked it to the OP :good:

IMHO I prefer the GNexus in terms of audio compared to the N4. I'm not sure why but I think it's because I got too used to the GNexus probably.
[Samsung Galaxy Nexus] osm0sis:
So while I'm updating here, what's the story on AwesomeBeats? Does it only work in /system, or can I put it in /data so that users can remove it more easily?
[Samsung Galaxy Nexus] Misledz:
System apps only as far as it worked else it just doesn't show up or says it's not installed. I included the updated one so the FC kinda has stopped. :eek:
[Samsung Galaxy Nexus] osm0sis:
Cool. Check my PM for a link to the duplicate files.. most of them aren't the same (different MD5) and have different dates, so seeing as you probably know which ones are supposed to be in there based on the date, just let me know and then we're set. :)

Edit: Happy to report your suggestion to go with the newer duplicates (V7B5? :D) resolves the slight lag I felt the mod brought with V7B4. :good:
[Samsung Galaxy Nexus] Misledz:
Thanks to [MENTION=4544860]osm0sis[/MENTION] for this trimmed build.

NexusLouder V7B5

- Performance hotfixes

- Removed duplicate files (Caused some minor slow down issues)

- Removed conflicting Volume.db (Causes issues with some players and BT unable to lower volume steps)

If all checks out, will consider this RC2
[Samsung Galaxy Nexus] osm0sis:
osm0sis approved, suckaz! :laugh:
[Samsung Galaxy Nexus] Prasad:
Sweet! Will test it today with Poweramp. :cool:
[Samsung Galaxy Nexus] gummie:
I'm happy that I'm not the only that one who notices those options merely had any effect when enabled and tuned. That is why I use another sound mod to reproduce the effects that I want.

I just have to ask this, will the uninstaller of the last version also remove the said conflicting files or should we consider wiping system and do dirty flash rom before this update?
[Samsung Galaxy Nexus] namtombout:
Wipe, flash revert, reboot then wipe, flash 7b5, or wipe, flash both, reboot?

U.O.E.N.O
[Samsung Galaxy Nexus] osm0sis:
It will, but it will also remove some stuff it isn't supposed to (which I fixed in B5). Definitely revert, then dirty flash your ROM if you care about having proper file backups for future updates, then flash V7B5 to get that all sorted out.

---------- Post added at 11:35 PM ---------- Previous post was at 11:33 PM ----------

No need to wipe anything. The install and revert both wipe cache and dalvik as part of the process. No need to reboot in between either.
[Samsung Galaxy Nexus] gummie:
I'm just a sucker on having clean file system so just made revert-wipe /system, /cache, /dalvik and resume dirty flashing everything. Thanks anyway for clarification.
[Samsung Galaxy Nexus] danvrez:
so if im going to update pa i need to

flash the revert

falsh the update and gapps

flash b5

flash ak kernel

wipe cache/dalvik

is it correct?
[Samsung Galaxy Nexus] Prasad:
Flashing the ROM update would bring it back to stock configuration, not to mention replace the kernel as well. Changes have been made accordingly as you can see above.
[Samsung Galaxy Nexus] Sparx639:
Hey misledz, I just wanted to let you know that I upgraded to v7b5 and I got stuck at the nexus logo for like 2 hours, but I then rewiped cache and dalvik and it booted fine. I had flashed the revert and then the new zip in one session, do you think that could have caused it?
[Samsung Galaxy Nexus] Prasad:
Happens sometimes with flash packages, even ROMs. A dirty reflash after a battery pull usually solves it for me.
[Samsung Galaxy Nexus] Sparx639:
I just wasn't sure if it was something I should point out or not, but yeah, that's what solved it
[Samsung Galaxy Nexus] Misledz:
Normally I tend to do the same really. Revert, followed by next in line being the mod. Probably just a glitch with twrp
[Samsung Galaxy Nexus] Xphazer:
Hi guys. :)

Starting with June 25 CarbonRom nightly build, the mod will cause a bootloop.

I tried pretty much anything I could think of, V7B3, V7B4, V7B5, June 25, 26, 27, default CarbonRom kernel and Franco. June 24 is the last build that the mod is working for me.

Here is a logcat of CARBON-JB-NIGHTLY-20130627-0258-maguro (default kernel) with NexusLouderV7B5.

https://www.dropbox.com/s/p66c58zqisjjh45/logcat.zip

Thanks a lot !
[Samsung Galaxy Nexus] daxisalive:
I tried the latest v7b5 with stable cm 10.1 and the bass when I enable in awesome beats the bass is really distorted. Anybody else?
[Samsung Galaxy Nexus] Ci-Fi:
I also have been experiencing bootloops with CarbonROM nightlies and this MOD. Let me know if you need a logcat from me as well.
[Samsung Galaxy Nexus] Misledz:
On the N4 we tackled this issue and fixed it same day. [MENTION=2977728]carepack[/MENTION] found the solution.

You would need to flash the previous nightly. Which is probably 23/25 then flash the gapps and the mod. Let it boot, and let it create dalvik and cache. After reboot to recovery and flash the 26th nightly along with the mod, then reboot.
[Samsung Galaxy Nexus] Misledz:
Mentioned the solution above bro, sorry I couldn't quote using Tapatalk 4 posts from the last page. For some reason it only allows same page quoting
[Samsung Galaxy Nexus] StormIceX:
why the OR in in red when you say is compatible for deoxeded and oxeded? my stock rom with ak kernel is fully compatible?

EDIT: yes it works
[Samsung Galaxy Nexus] Ci-Fi:
I'm a little confused. Since I'm on currently the 6/20 nightly of CarbonROM, I should flash the 6/19, GApps, & MOD? Then let it reboot and then flash 6/20 nightly & MOD and reboot? What if I'm planning to flash the 6/28 nightly, what should I do then? Thanks for your help.
[Samsung Galaxy Nexus] 5F55:
bootloop on cm10.1

I have problems installing Nexuslouder V7B5 on my Galaxy Nexus. I run cm10.1 Jellybro with Trinity kernel and TWRP 2.5.0.0.

I have flashed V7B4 builds without any problems in the past so when I a few days ago went back to Trinity kernel after testing Lean Kernel and done a clean install i can no longer install Nexuslouder the only thing that happens is that I get bootloop. I think it has to do with the DSP . Love your work sorry for my english.
[Samsung Galaxy Nexus] greyhd:
Did you do the revert?
[Samsung Galaxy Nexus] 5F55:
bootloop on cm10.1

No.

I did a factory reset then installed Rom, gapps, gpu files, kernel and Nexuslouder.
[Samsung Galaxy Nexus] greyhd:
Do the same except the Nexus louder mod. Set your phone up the flash the mod last.
[Samsung Galaxy Nexus] PhoenixBurn:
Where is V7B1 Revert ?? Please reload this file ? Thanks
[Samsung Galaxy Nexus] Coolgoly:
post 3:

http://d-h.st/users/Misledz/?fld_id=15787#files

edit:oops...there's no v7b1 version.
[Samsung Galaxy Nexus] Misledz:
Blopblop it works for both

Yeap that's the correct sequence, honestly i'm dead confused as originally I thought I had to remake for the new changes, but when carepack did the solution he got mass trashed as people thought he was trolling till he posted up a screenshot. As for the 28th nightly, the problem only started with the latest builds (27th onwards) so that would be the last version it worked on + gapps + mod, let it boot and create, then latest nightly + mod. That should do the trick.

Nope it's the latest build of CM10.1

It's a little different with the new builds that are based off CM10.1's update.

Copy pasting it from the N4 side by carepack

1. boot into recovery

2. wipe -> factory reset

3. install -> previous nightly ROM build

4. add more zip -> kernel (if you use one)

5. add more zip -> Nexus Louder

6. system is going to boot -> playing around for a while

7. boot into recovery once again

8. install -> flash new nightly

9. add more zip -> kernel again (Since it gets re-written)

10. add more zip -> Nexus Louder

11. voilá -> system boots up
[Samsung Galaxy Nexus] Misledz:
Notice, All ROM's branched from the CM10.1, after checking logs and githubs, a member had posted the following.

The following changes will apply from next nightly.

android_hardware_qcom_audio-caf 2013-06-28 14:25:36

Merge "audio: provide a hook for audio amplifier implementations" into cm-10.1"
[Samsung Galaxy Nexus] MaLiXs:
A little ot.. But this live wallpaper need to be shared for all music lovers https://play.google.com/store/apps/details?id=com.androidgamer.albumart

Send from my Pure Franco GNex
[Samsung Galaxy Nexus] Xphazer:
Thanks it's working !

I flashed June 24 build + GApps + Multi DPI Play Store + Franco 382 + V7B5.

Booted into the ROM.

Went back in the recovery and flashed June 28 build + Franco 382 + V7B5.

Its working, but this sound like a temp fix to me. :)

I hope that it will be easy to solve. ^^

Thanks a lot for your work !
[Samsung Galaxy Nexus] Misledz:
As I mentioned earlier, when CM will fix the commit in their next nightly, and carbon will follow:good:
[Samsung Galaxy Nexus] nex_t:
I cannot make this MOD to work, except with Sourcery ROM. I wanted to install ATOM ROM / CM 10.1 / but as i said, this MOD doesent work.

Would you help me, please ?
[Samsung Galaxy Nexus] Misledz:
Dude...Did you not read and just post? If you looked above you like 3-4 posts the solution is there.
[Samsung Galaxy Nexus] daxisalive:
[MENTION=4118822]Misledz[/MENTION] so what does it mean for this mod? Is it gonna have compatibility issues?
[Samsung Galaxy Nexus] Misledz:
It just means that the MOD never had an issue in the first place, its the commit that got included into ROM nightlies caused it to have an issue, that will be fixed by them, the reason dirty flashing worked is because the older commit got loaded and replaced the newer broken one.

ATM the only solution has been posted a few posts back.
[Samsung Galaxy Nexus] 5F55:
bootloop on cm10.1

I can't get it to work. Here is how i did

1. Factory reset

2. Installed rom and gappas

3.installed kernel

4. Installed nexuslouder.

5. Let system boot.

6. Boot into recovery

7. Installed new rom and gapps

8. Installed kernel

9. Installed nexuslouder

10. Let system boot.

Do i need to wipe anyting More?
[Samsung Galaxy Nexus] namtombout:
Just wait until your ROM is updated with the cm fix or use a version of your ROM that was built on or before 6-26

U.O.E.N.O
[Samsung Galaxy Nexus] Misledz:
Best solution given so far, rather than going through all this hassle. I doubt theres anything godly about the latest nightly that would make them want to go through all the trouble.
[Samsung Galaxy Nexus] MaLiXs:
For me the latest release is by far the best that i have tested... i use this mod ilsince I early v6 version (doesn't remember which ome exactly).

I can't let my phone without flashing it!

Again thank misledz (and other modder) to let us have a really good sound for our beloved gnex

Send from my Pure Franco GNex