yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] hidato_aori:
Don't mention me, I am not existed. Lol I hate here (community) very much. I only respect Fritz and visit once a while... I also get annoyed with that question 「which do you recommend, X or Y.」, 「Why its sound so low ?」…… get an AMP you poor guy, since you are rich to get new device, your ears are damaged, you should see a doctor. Kinda of childish question like baby. Usually, their email is set to auto junked, filtered by content. I am getting this kind of email about hundred everyday. I suggest if you are not practically a portable audiophile, and very experienced one, please stay away of those products. Not fritz's handcrafts, mine...
[Samsung Galaxy Nexus] osm0sis:
Worth a try. The script grabs the zip path as exported by the recovery so if that was somehow wrong, that would cause a problem. To test that I'd have to make a special zip though. We'll try that after the things I'm about to suggest. The f*cked thing is I'm sure you guys can flash the latest SuperSU via recovery? I use the exact same method Chainfire does, so ..

a) If you could try uninstalling SuperSU and then flashing the SuperSU 1.80 zip again to see if it works correctly that would be appreciated.

If it's the same as before with /system/etc/.nexuslouder getting written but basically empty then it really seems like an issue with the unzip command extraction to /tmp/nexuslouder which, if we're all using the same recovery like the latest TWRP 2.6.3.2 and CWM 6.0.4.5 (I tested both on JB and KK), should work fine. Of course the confusing part is that doesn't seem to be the case for a few.

b) If you guys who can produce the issue could put the zip on your sdcard, boot to recovery, adb shell in (or AROMA Filemanager's Command Terminal might work) and type the following commands I'd appreciate the outputs:

mkdir -p /tmp/nexuslouder

cd /tmp/nexuslouder

unzip -o <path to NL zip>

cd /tmp/nexuslouder/patch/

find . -type f

c) Here's another good question, toro, toroplus, or maguro?

I've been testing all this on maguro but maybe there's some bullsh*t reason the other two are sh*tting the bed in some of their recovery builds where maguro doesn't. I've been over the script a hundred times so there's no bugs or typos, there's just some weird sh*t going on with some devices we clearly need to work around.
[Samsung Galaxy Nexus] bcote311:
The only thing I did to get this running on the latest Slim 4.4.2 was the same way I have always done it. Clean flash, boot into and set up rom, then go into and recovery and flash this along with my kernel of choice. I use Awesomebeats so I just deleted the others. I noticed there wasn't a place under Sound to select Awesomebeats like there was on 4.3 and before but when I select equalizer from Play Music it pulls up just fine. The mod sounds great as usual and I really appreciate the hard work you do Misledz, Osm0sis, and whoever else may have helped! Really looking forward to flashing this on my N5 and 4.4.2 N7!!
[Samsung Galaxy Nexus] Sheetzie03:
Ignore these idiots my man. Some ppl are really something else. I DO NOT blame u at all. I would love for you to give me their usernames because I would give them a fat ass piece of my mind.

Sorry you have to deal with these complete wastes of life.

Beside I prefer THIS MOD AAAALLLLL DAY over viper.

To those who sent the pm's: get a gd life, and pm if you'd like.

This mod is amazing. Couldn't think up enough adjectives to describe it and you for that matter.

A heart felt thank you to you [MENTION=4118822]Misledz[/MENTION]

♦ToroNex-KK°D♦
[Samsung Galaxy Nexus] lambofgod13:
I'm deaf in one ear and hell, i can tell the difference in ezio and viper smh. Thanks for your hard work mizled you've always put out good audio stuff bro :thumbup:
[Samsung Galaxy Nexus] RedDeadDorito:
Software/Hardware hack > A program you install
[Samsung Galaxy Nexus] Misledz:
I doubt Option C really matters because Sheetize and all are using a toro and it works for them.

Option B that might work but perhaps we are overlooking the problem could be with the recovery itself writing to a sector, failing because there's not enough space but it doesn't output an error. The same thing happened with Titanium Backup. I made a zip backup file and used it. It returned positive value and success but when I checked the app drawers, there were no apps from the backup installed. Turns out the error lied in two things, SUPERSU and BusyBox (some roms tend to have it integrated)

Perhaps a clean flash from Slim Kat should fix the issue. I know people prefer to dirty flash as it saves time. But perhaps the initial problem was there with older builds and dirty flashing never really solved it.

There is another solution. Have them flash the test build the farm generates to see if they get it to work. If it installs properly then something with the signed one is causing conflicts.
[Samsung Galaxy Nexus] xxSAKISxx:
hey Misledz i follow this thread and your work since i get my nexus from 4.2 jb and i must say that this mod is a MUST HAVE for everyone. Now i jump from 4.3 stock to cMetal 4.4.1 and i just flash V9beta1 but (i know some friends mention it few posts above) i don't get any apps like eizo or awesome beats. Another thing is that cMetal have a dsp manager build in and even when i go to play music eq this dsp manager pop up. i make something wrong? i really appreciate yours and osmo and who else put his knowledge to make this perfect mod. Pls if i must do sometging so make this mod work let me know mate. Abig thanks for all of you guys.
[Samsung Galaxy Nexus] osm0sis:
Those aren't options, those are actually 3 things I want to know from everyone having the problem. Though you're right c) doesn't appear to matter but I wanted to know anyway just in case. :)

Test build isn't useful for troubleshooting because it still uses EDIFY like Farm 1.0. There is no "legacy" in recovery and su has no bearing there.

I can almost definitively tell from what is left behind (the empty .nexuslouder and unchanged build.prop copy) that the fault is with unzip. The question is why and how to fix it.

So please [MENTION=2210914]xxSAKISxx[/MENTION] [MENTION=4870668]JuggaloDroid[/MENTION] [MENTION=4454119]t1.8matt[/MENTION] [MENTION=4885250]sajty[/MENTION] [MENTION=3548609]spacemanr[/MENTION] please follow my instructions from my previous post and report back.
[Samsung Galaxy Nexus] t1.8matt:
[MENTION=1143630]osmosis[/MENTION], I am running Omni Rom 4.4.2 on Toro with SuperSU 1.80. I do have the nexuslouder file in system/etc at 62 bytes. Basically empty, this is what's in it:

# Conflicts-List

# Rename-List

# Delete-List

# Dir-List

In going to have to try option b after work.
[Samsung Galaxy Nexus] xxSAKISxx:
i confirm. i run cMetal 4.4.1 and this is what nexuslouder have inside.
[Samsung Galaxy Nexus] osm0sis:
Guys that's not what I asked. Give me the answers to a b and c:

http://xdaforums.com/showpost.php?p=48443093&postcount=7061
[Samsung Galaxy Nexus] xxSAKISxx:
osmo i can try b with terminal emulator on my phone beacuse i am not in front of my pc atm?
[Samsung Galaxy Nexus] osm0sis:
Nope. Terminal emulator doesn't tell me anything. It needs to be from in recovery. Download AROMA Filemanager, boot to recovery, flash it and open its command prompt. That should give me the same info without needing USB adb shell access.

You can even take screen shots in AROMA by holding the volume down then power button.
[Samsung Galaxy Nexus] JuggaloDroid:
I will get back to you with this report as soon as I am able. Things are a bit hectic but thank you for your continued support on this :good:
[Samsung Galaxy Nexus] spacemanr:
well as i don˙t follow you guy˙s what you˙re talking about i˙ll just say that i wiped all over again, installed rom CM unofficial again, different gapss, mpokang kernel V10 super ram, and again this mod but again without luck :(, again there is no awesome beats or anything else, damn.
[Samsung Galaxy Nexus] t1.8matt:
[MENTION=1143630]osmosis[/MENTION], this is what i got when doing step b.

And step c is Toro

Please let me know if I did anything wrong and I will try to correct it.
[Samsung Galaxy Nexus] osm0sis:
Nailed it. I don't know why or how to fix it but that short read error is the cause of the issues for some. Thanks!

What about step a) ? Does SuperSU install okay from the zip? Uninstall it first so you can be sure how it worked.

Can you also checksum the zip to make sure it's intact?
[Samsung Galaxy Nexus] t1.8matt:
Yes, I always install SuperSU from the zip, and it's working fine. Which zip to checksum, SuperSU or NexusLouder? Not sure how to get checksum. If you mean the MD5 checksum I have it from the NexusLouder zip and the SuperSU zip, just don't have anything to compare them to.
[Samsung Galaxy Nexus] Misledz:
I came across something when searching for that short read problem, this guy managed to solve the problem

http://lists.busybox.net/pipermail/busybox/2008-January/063988.html
[Samsung Galaxy Nexus] xxSAKISxx:
So i guess the solution to make this mod work is close. cool
[Samsung Galaxy Nexus] Sheetzie03:
Currently running cm 11 skank 4.4.2 12-13 by fitsnugly Banks latest standard gapps mpo1080p

Did not flash su 1.80, no other mods

Always clean flash.

Run superwipe zip. Factory resest.

Flash ROM, gapps, kernel. Reboot

Reboot again after letting sit about 5 mins.

Setup. Reboot recovery.

Flash mod. Reboot

Use Beatz so freezed Dolby and Eizio.

Kept noozy. Did test with Noozy after setting external. Played song. Then opened audio effects and it opened Beatz because it was the only left installed.

Adjust settings in Beatz while song was playing in Noozy and did NOT notice any changes, so I thought it might not have worked.

Then I opened Apollo which was the only other music player I had installed, played song, opened audio effects via Apollo, Beatz opened. Adjusted settings, and its working fine. Not sure if noozy only works with the built in DSP or doesn't work with Beatz, or maybe it does work, and that I had to retry Noozy with beats.

All I know is its working.

Below is my built prop. Not sure what its suppose to say but thought I should post anyway just in case.

Lastly, have not tried any other ROMs like slim or omni with the latest version. Of this mod so I can only speak on it working perfect with the above cm11 rom. However, I hope things get worked our for ROMs that aren't working because I'm sure I'll be changing dd soon enough.

[MENTION=4118822]Misledz[/MENTION], CANT SAY IT ENOUGH,

T.H.A.N.K. Y.O.U. ✖ ? ????????

?Turnt Up-KK Metal with THE best Audio Improvement Patch out there&#8596 [MENTION=4118822]Misledz[/MENTION] Xlouder?
[Samsung Galaxy Nexus] subaash:
can u send me the link for the mods and also the superwipe zip..thank you..couldn't find it anywhere..
[Samsung Galaxy Nexus] Misledz:
You make me all warm and fuzzy inside. Might be gas :P

:good:

Have you seen Page 1 yet?
[Samsung Galaxy Nexus] Nephilim:
Just wanna say thanks so much for the hardwork you and osmosis put into getting this amazing mod working on 4.4.x so fast!!!

Sent from my Android 4.4.2 Galaxy Nexus
[Samsung Galaxy Nexus] Sheetzie03:
as far as the superwipe zip, cant send it to u right now but if you go to this one website google. Com? and search: Super Wipe Galaxy Nexus toro .zip

It shouldn't be too much trouble to find.

And then the other stuff you want, refer to [MENTION=4118822]Misledz[/MENTION] 's qouted post of yours.??

?Turnt Up-KK Metal with THE best Audio Improvement Patch out there&#8596 [MENTION=4118822]Misledz[/MENTION] Xlouder?
[Samsung Galaxy Nexus] 47th_Ronin:
I got it working on shiny.

Tried it on the same build once before and it was a no go, however this time after I'd set everything up i also installed xposed framework and and instead of just rebooting i went into recovery and flashed inmans mod and then Xlouder

(Didnt think it would work tbh)

Thats the only thing that i did differently this time....

So maybe something to do with the framework?

Idk but i haven't tried this on any other rom so it may be just a fluke.
[Samsung Galaxy Nexus] dimkav:
I also use xposed framework and the xlouder works like a charm.

I flashed cmetal 4.4.1 then pa gapps and supersu, then i installed the xposed framework.

After the set up of the framework I flashed xlouder and works super.
[Samsung Galaxy Nexus] spacemanr:
Hm, I've had the xposed on 4.3 and flashed xlouder which worked fine but didn't even thought about that it might be the reason. Will try and report.
[Samsung Galaxy Nexus] Sheetzie03:
With some problems ppl are having, This is just an Informative post regarding this mod.

Didn't want to quote my post a few before this because of how big it is so please reference to that if you need to.

So I tried my 2nd toro ROM(1st was CM11 by fitznugly), OmniMetal 4.4.2, with the latest version of this mod.

Same Installation steps. Same result. Installs/Works as its suppose to.

No problems. Thanks❗

?Turnt Up-KK Metal with THE best Audio Improvement Patch out there↔@Misledz Xlouder?
[Samsung Galaxy Nexus] t1.8matt:
I tried what you did on FML ROM, still no go on the patch working. Guess I'll see what happens after Misledz and Osmosis mess with it some more.

---------- Post added at 03:17 PM ---------- Previous post was at 03:09 PM ----------

After flashing the zip though, I just noticed I have 2 build.prop files. Build.prop.NLbak, and Build.prop. No NexusLouder changes are in either file.
[Samsung Galaxy Nexus] gpzbc:
Just discovered this mod. Thank you so much!
[Samsung Galaxy Nexus] osm0sis:
[MENTION=4454119]t1.8matt[/MENTION] Yup. That's because the build.prop changes only come from a file that's supposed to get unzipped but isn't, as you confirmed. Same goes for the stuff that's supposed to be in .nexuslouder. Weird thing is that the SuperSU zip works where mine doesn't, since the only difference between what Chainfire and I have done is maybe that he might not use 7zip (7za.exe) to pack, he might use something else in Windows. Still weird, since it's all standard, and it's proven working on most devices. Either way, I guess I could ask him, so that I can try and copy his procedure completely...

But first: can you please post a link to the exact recovery image you're using so I can try to reproduce the issue with it? Also please detail the rest of your setup so I can duplicate it. Also do you use Xposed? What busybox do you have installed to your system and where?

I checked out the "short read" link [MENTION=4118822]Misledz[/MENTION] posted and unfortunately the solution for those guys was to switch to gzip and/or patch, which we can't do since recoveries read only flashable zips packed by info-zip (the standard pkzip zip format), and we just use the supplied unzip/busybox binary that is packaged with the recovery and obviously can't unpack our own. :p

Here's a semi-interesting thread of the exact same issue but for a gapps package: http://code.google.com/p/openetna/issues/detail?id=385 but unfortunately they never post a solution, just marked it resolved since people stopped complaining. ;)

Can you try these commands (like last time) and see if you still get short read errors?

mount /system;

mount /data;

mount /cache;

mount -o rw,remount /system;

mount -o rw,remount /system /system;

mount -o rw,remount /;

mount -o rw,remount / /;

mkdir -p /tmp/nexuslouder;

cd /tmp/nexuslouder;

unzip -o <sdcard_path_to_NL_zip>

if the first block of commands still give the error, also type: unzip --help

and then: /sbin/busybox unzip -o <sdcard_path_to_NL_zip>

:good:

I've got another possible solution idea if none of that works, but it would involve relying on your ROM containing busybox in /xbin/ so is also not ideal. And I could make it conditionally fallback to the ROM's busybox unzip, but we're getting hackish, which I'm not a fan of doing.
[Samsung Galaxy Nexus] thenewguy821:
On cMetal 12/3 build, I was having the same install problems people are describing here (says install successful in recovery, but no apps added, no change in volume, .nexuslouder having just the header scripts but no other info). I switched to latest TWRP, and the mood installed fine. When I switched to the 12/7 build, still on latest TWRP, the flashing problem returned.

---------- Post added at 05:55 PM ---------- Previous post was at 05:52 PM ----------

Have a link to exposed framework? I will try this as well... Also, is xposed working with ART enabled?
[Samsung Galaxy Nexus] t1.8matt:
I'll have to post up the zip I used to install TWRP 2.6.3.2 either later tonight or tomorrow, same with running those commands. Busybox is preinstalled on the ROMs I've used, I've never installed busybox. Its 1.21.1-kk in system/xbin. I do use xposed, running the latest update.
[Samsung Galaxy Nexus] osm0sis:
:eek:

Yeah this is a weird ****ing problem. :confused:
[Samsung Galaxy Nexus] t1.8matt:
Could this be a problem with 4.4.2? Is everyone who is installing it with no problem on 4.4.1?
[Samsung Galaxy Nexus] dimkav:
The xposed framework you will find it very easy by searching for it on Google.. Sorry i cannot send you the link at this moment.

I am using the cmetal 12/7 and the xlouder mod works super. Crashes when I try to switch it by music effects but it seems to works automatically and the sound is obviously much better! It's not my idea :P
[Samsung Galaxy Nexus] t1.8matt:
Since people are having luck on Cmetal 12/7 I'll flash that and give it a try. I've also been using Slimkat and Banks gapps so I'll try Paranoid gapps as well.

---------- Post added at 07:30 PM ---------- Previous post was at 07:29 PM ----------

Think maybe its worth a try to downgrade 1 version of TWRP and see if that works?
[Samsung Galaxy Nexus] osm0sis:
Nah it's happened since 4.4, so that's out, and there's definitely no rhyme or reason to toro vs. maguro.

Yes. Worth a try, but you're the one guy who I've got here who can use adb shell and reproduce it reliably, so please try my other suggestions first. ;)

P.S. Shout out to [MENTION=4840431]Ci-Fi[/MENTION] who rarely posts but must be spending pretty much all of his daily Thanks quota on my posts here while I've been trying to fix this. :cool::o:D
[Samsung Galaxy Nexus] t1.8matt:
This is what I got in ADB Shell
[Samsung Galaxy Nexus] osm0sis:
You got the path to the zip wrong, please try again. (It's failing because of the spaces in the directory name). Thanks for all the help! :)

Edit: [MENTION=4454119]t1.8matt[/MENTION] Sh*t! I just noticed you did something similar the first time you tried the commands. :(

http://xdaforums.com/showpost.php?p=48458326&postcount=7076

You had "/sdcard NexusLouderV9Beta1-Galaxy_Nexus.zip" instead of "/sdcard/NexusLouderV9Beta1-Galaxy_Nexus.zip"

So please try the original commands from b) in my other post again but be sure you've got the proper path to the zip; since "short read" probably wasn't the actual error for our zip problem. Then you can go ahead and try the new list. :good:
[Samsung Galaxy Nexus] dracon6ai:
Just to add to the madness, everything worked like a champ on the 4.4.2 version of Shiny (Toro). Using CWM touch.

***Laziness is nothing more than the habit of resting before one gets tired.***
[Samsung Galaxy Nexus] t1.8matt:
Ok, just did step b over again, way different result. How can I save my adb shell session to a file as it's way to long to show in a screenshot.
[Samsung Galaxy Nexus] Prasad:
V9 Beta 2 works like a champ on latest OmniRom nightly from [MENTION=2999829]PlayfulGod[/MENTION] ! :D
[Samsung Galaxy Nexus] t1.8matt:
Well Osmo, after redoing step b and the commands on the last page you just gave me, both end like the screenshot below. Both unzip the same way, I just don't know how to save my whole adb session to a text file so you can see the whole thing.
[Samsung Galaxy Nexus] osm0sis:
You can add: > /sdcard/log.txt

to the end of every command then post log.txt on pastebin

:good: :D
[Samsung Galaxy Nexus] t1.8matt:
every single command? Just want to be 100% sure on this before I do this again.
[Samsung Galaxy Nexus] osm0sis:
So the crazy thing here is that means IT WORKS! :D

Now that you've definitely got the zip in a path with no spaces can you go ahead and delete the empty /system/etc/.nexuslouder and then try to flash the zip and see if it's still not working?

---------- Post added at 09:53 PM ---------- Previous post was at 09:52 PM ----------

Yes, but actually it needs to be: >> /sdcard/log.txt

That will make sure each command's output appends to the end of the last.
[Samsung Galaxy Nexus] t1.8matt:
I think we have liftoff, it's taking way longer to install, every other time it was like hyper install, took only 2 seconds, now it's like 10-15 seconds.........Rebooting.....Android is upgrading...................damn, stuck on Starting Apps. Restart and a bootloop. Hmm, wipe and try again? Seems like it was gonna work.

---------- Post added at 09:23 PM ---------- Previous post was at 09:02 PM ----------

Besides switching to CWM to see if it works, I seen Metalspring suggest to someone else having issues to mount /system first and then flash it, would that make a difference?
[Samsung Galaxy Nexus] osm0sis:
Shouldn't since the zip script has those mount commands built in already.
[Samsung Galaxy Nexus] t1.8matt:
i dunno then. I'm gonna clean flash again and see what happens.
[Samsung Galaxy Nexus] osm0sis:
Before you clean flash check /system/etc/.nexuslouder and /system/build.prop to see if things wrote correctly this time. There should also be some .NLbak files in /system/etc/ (among many other places) if things at least installed how they should. Worth knowing the install sort of worked even if it doesn't boot.
[Samsung Galaxy Nexus] JuggaloDroid:
[MENTION=4544860]osm0sis[/MENTION] I performed step a) and lost root somehow but got it back. I can flash other zips in recovery just fine. I tried flashing the beta again with the same results.

I'm trying to do step b) and I'm in adb shell but can't seem to figure out how to input where my NL zip is. I have it in a folder APK's Kernels & Zips/Nexus Louder but I'm clueless as to how I input that.
[Samsung Galaxy Nexus] osm0sis:
I have the growing feeling that the issue for all you guys has something to do with the spaces you have in your zip paths... I think I can fix that. :fingers-crossed:

Trying to reproduce it on my side.

And for future reference, you're likely to run into fewer problems overall in Linux-based systems if you don't make files and directories with spaces in the names. :)

---------- Post added at 11:03 PM ---------- Previous post was at 10:57 PM ----------

**** yes! Reproduced. On it. :D:D
[Samsung Galaxy Nexus] t1.8matt:
I see you might have a fix, but how can I check those things when I'm in a bootloop? Am I able to pull them with adb in recovery?
[Samsung Galaxy Nexus] JuggaloDroid:
Fixed It!!! :victory: I took out all the spaces and other odd characters in my file path and it installed it with no problems. Everything seems to be up and running. Apps are all there and now it's just a matter of testing. Thank you so much [MENTION=4544860]osm0sis[/MENTION] & [MENTION=4118822]Misledz[/MENTION] for all your assistance and support.:highfive:

---------- Post added at 10:19 PM ---------- Previous post was at 10:18 PM ----------

Try going back into recovery and flash the revert zip. That may fix the bootloop.
[Samsung Galaxy Nexus] osm0sis:
Yup. In recovery you have complete filesystem access. Type:

mount /system;

cat /system/build.prop;

cat /system/etc/.nexuslouder;

There should be lines at the bottom of the build.prop related to XLoud and .nexuslouder should be full of a huge list of filepaths. :good:
[Samsung Galaxy Nexus] t1.8matt:
yes, everything did write correctly, just bootlooped on me. so all you did to fix it was rename the zip without all the unecessary characters?
[Samsung Galaxy Nexus] osm0sis:
It's the spaces in your folders/directories. It was always the spaces.

I've confirmed my new Louder Farm 2.0 scripts now accounts for this and installs perfectly. I also added some extra error catching logic so that if something like that does go wrong it won't proceed with the install anymore. :good: :cool: