yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] nex_t:
[MENTION=4118822]Misledz[/MENTION], excuse me but i don't know what do you mean.

Would you explain it, please ?

What am i doing wrong ? I am a beginner, i don't know exactly how to replace / flash a new ROM.

I will tell you shortly the way i do : reboot to recovery / Wipe / Dalvick cache ( i thick cache as well )

After that, i install the new ROM / gapps /

---------- Post added at 06:42 PM ---------- Previous post was at 06:37 PM ----------

Which one is the latest release and where did you download it from ?

I have the version NexusLouder V5Omega, from here :

http://xdaforums.com/showthread.php?t=1748803
[Samsung Galaxy Nexus] bombadier:
If you are using V5Omega (Which is the latest for 4.1 ROMS)then you must be running a 4.1 ROM, MaLiXs is on a 4.2 ROM and that version can be downloaded from the third post but that is only for Android 4.2 so do not flash
[Samsung Galaxy Nexus] MaLiXs:
I'm using v7b5 on 5.6.1 purity with latest franco kernel

Send from my Pure Franco GNex
[Samsung Galaxy Nexus] nex_t:
I just downloaded v7b5 Nexus Louder / Atom ROM / AK kernel / is not working

As i said, the only ROM i can use with NexusLouder, is JBSourcery. But i wanted to change the ROM, and the loud for the ringtone is very important for me.

I have no idea what else i can try.
[Samsung Galaxy Nexus] jesssiii:
There was a problem with linero ROMs with the last version. The solution was to use one of the previous versions. I think it was b2?

Toro GNex
[Samsung Galaxy Nexus] nex_t:
I tried with b2 as well. Same story.
[Samsung Galaxy Nexus] Misledz:
Just use the previous nightly till they fix the CM commit
[Samsung Galaxy Nexus] MaLiXs:
since I've update to purity 5.7, if I flash the mod I'm getting stuck on bootscreen without being able to boot

There have someting to do with that issue ?
[Samsung Galaxy Nexus] Follomon:
Just used the smart updater to update to purity v5.7 and then wiped cache and dalvik and then flashed nexus loader v. 7beta5. Wiped cache and dalvik again, rebooted and fix permissions. Everything is working good.

Gesendet von meinem Galaxy Nexus mit Tapatalk 4 Beta
[Samsung Galaxy Nexus] MaLiXs:
if i flash the nexus louder I cant reboot to rom ... did you only reboot to recovery ?
[Samsung Galaxy Nexus] Follomon:
Rebooted into recovery and then fixed permissions. Then rebooted to rom. Everything working like it should

Gesendet von meinem Galaxy Nexus mit Tapatalk 4 Beta
[Samsung Galaxy Nexus] MaLiXs:
I'll try in that way
[Samsung Galaxy Nexus] mesruh:
Same situation here, I am trying the proposed solution as well.

---------- Post added at 11:58 PM ---------- Previous post was at 11:50 PM ----------

I didn't work for me, same bootloop. :(
[Samsung Galaxy Nexus] MaLiXs:
well I think i'm gonna give up really tired of that ... Itried many way but any is of those are not succesfull for me I Also tried to flash with cwm instead of TWRP... I'll miss this mod
[Samsung Galaxy Nexus] Misledz:
Don't rush it. You're supposed to dirty flash the rom update and the mod. This is due to the cm commit that needs to be fixed.
[Samsung Galaxy Nexus] Sparx639:
These kids. Always eager to give up huh?
[Samsung Galaxy Nexus] Misledz:
Hahah yeah its hard to choose because if I make the change to the commit then PA and AOSP users will bootloop. But aokp users will be fine. But the dirty flashing method seems to solve all the problems. So it's dead hard to choose a side.
[Samsung Galaxy Nexus] MaLiXs:
Like i said whatever I do i got my device in bootloop including dirty flashing

Send from my Pure Franco GNex

---------- Post added at 09:31 AM ---------- Previous post was at 09:21 AM ----------

Sometimes i prefer a early give up than throw my device on th wall.. Seriously i want keep things simple. If im give uo it because i work on it the whole afternoon

Send from my Pure Franco GNex
[Samsung Galaxy Nexus] AbhishekS:
LOL! I feel sorry for myself now. I wasted around 4 hours for the bootloop of my phone. Constantly kept on feeling that something is wrong with the kernel as the mod was working fine with the same ROM version earlier (I had dirty flashed the ROM earlier).

Finally I know what the issue is and a temporary fix.

BTW, till the CM team and their derivative ROMs fix the issue, can you please provide two versions of your mod? As in one compatible with PA/AOKP and other with those using CM as a base. If making two versions can be achieved by just minor changes and modifications of a file or two, then please do so. It's a sincere request and I believe it will help many CM users.

Thank you. :)
[Samsung Galaxy Nexus] xxSAKISxx:
i just upgrade from PA 3.56 to PA 3.60 and the V5 works perfect. Always clean flash.
[Samsung Galaxy Nexus] bombadier:
Just Jelly Bean as the title suggests.
[Samsung Galaxy Nexus] KakashiSensei95:
Hello to all! Works on CyanogenMod 10.1 stable?
[Samsung Galaxy Nexus] Reginald476:
Works fine for me on 10.1 Stable with stock Kernel.
[Samsung Galaxy Nexus] Sheetzie03:
Next time, check the op, the answer might just have been there

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] AbhishekS:
Won't work on the latest nightly.
[Samsung Galaxy Nexus] Misledz:
I have decided to halt uploading new releases till there's some clear info on what's happening. Long story short, everyone's trying to merge 4.3 features without the proper source pack for it. It's like the race for "Who get's the ROM with the newest features first" and by doing so it starts to break stuff and you're not even sure anymore what's the cause.

The MOD does work with all ROM's with a

certain flashing procedure

, you just need to be patient enough to get it work. 90% of the latest nightlies are those combined with the leaks from the Google Edition phones, sure camera and such won't break anything, but just like how 4.2.1 had a huge changelog and massive incompatibility with 4.2.2, expect the same to roll for 4.3.

Pretty occupied with thesis defense lately and irl stuff taking it's toll which is why I haven't been as active lately, as much as i'd like to throw a nightly every now and then it's just not happening that fast.

Once the heat has cooled down in regards to leaks and such, that's the time i'll post a proper build. I have 3 builds atm but they aren't ready for consumer release as it works on AOKP/CM while it doesn't on AOSPA/AOSP, which therefore defeats the whole purpose of this MOD being "Universal", Understand that while most of you would say "Post it up so that CM/AOKP users can use it"--it's not that easy, and if you've been here on xda long enough, you'd find reading is a hard thing for some people to do, they walk in, flash stuff without reading, then cry a river/curse the developer/curse the work for their lack of comprehension, and posting these nightlies would just cause a rush of people to ask the most common "Upgrade process" despite it being the same since build #1, followed by flashing it on an AOSP/PA ROM causes a bootloop.

Thanks for understanding.
[Samsung Galaxy Nexus] Sheetzie03:
Its all good bro. Do what you gotta do, we'all still be here:D

OK [MENTION=4118822]Misledz[/MENTION] I was coming here to ask you a question and of course I read this post because it was the first unread post. I'm trying to figure out it if my question has connection or not. I don't 'think' but I could be way wrong. So I'll just go ahead.

This is what I posted in the BeanStalk Port thread for Gnex:

OK well I am a big fan of the xlouder audio improvement mod by [MENTION=4118822]Misledz[/MENTION]. I'm sure you've probably heard about it.

Anyway, I first discovered you're amazing Beanstalk Port starting with the 6-24 build and I Flashed xlouder mod with no problems at all.(BTW youre ROM is noticeably the loudest I've experienced- before any mods, thought that was interesting)

So now, with the 7-1 build, cannot get it flashed. Everything is done exactly the same as I did with 6-24 with 7-1, but with 7-1, Instead of :

reboot-google screen-beanstalk boot animation-boot into ROM

Its reboot-google screen-beanstalk boot animation-but it just hangs here.

Tried going back wiping caches again, fix permissions, rebooting,ect. Tried reflashing the mod. Basically nothing worked, I just couldnt get it flashed.

Do you have any ideas why this is happening? Did something change from 6-24 to 7-1 that could be causing this audio mod not to work?

_________________________________

I hope it was OK to copy/paste my post from over there to here. If you do not want me to do that anymore, no prob just let me know.

Thank you for your time Misledz. I very much appreciate it. And thank u for your hard work.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] Misledz:
It's all good man. Have you tried flashing without the mod then let it boot, followed by dirty flashing it again with the mod?

The freeze up is due to the different commit by cm that's why
[Samsung Galaxy Nexus] The Gingerbread Man:
Hi [MENTION=4118822]Misledz[/MENTION], back using your mod to boost ****ty speaker on my gnex. I got rid of noozy player and beats and using noozoxicde as my music engine with recommendation from Osmosis. I wanted to thank you as now I can actually hear when my phone rings and hopefully I'll be able to hear navigation voice when using it over 50mph lol! I'm a little curious about the Dolby mobile apk which I found comes bundled along in your package, could you shed a little light on it? I can't see much documentation about it only more places to download it. Obviously iv heard of Dolby but curious about this mobile buissness
[Samsung Galaxy Nexus] AbhishekS:
If you have the CM mod then please can you PM it to me if you are not willing to release it because it defeats the purpose of a universal mod?

I know my request sounds bad, but I'm really having a bad time. In all honesty, most of my calls go unanswered because I simply sometimes cannot hear my phone ringing.

It's a sincere request. Thank you. :)
[Samsung Galaxy Nexus] volcalstone:
Love your work [MENTION=4118822]Misledz[/MENTION]. Will wait for a fix. Running LS 2.80 with Franco and miss the mod. I might have to go back to LS 2.6.5 for rite now when your mod was working.
[Samsung Galaxy Nexus] Sheetzie03:
OK do you mean * flash rom on clean install(like always) let boot up, reboot recovery, then dirty flashing ROM, followed by wipe cache's, then flash mod?

If that's what you're saying, I have not did this. If you could please clarify if this is what you mean?

Thank you a bunch mate

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] BlackJou:
I've been trying to flash this in the latest xenonhd ROM and I just keep getting boot loops.. Any idea on what could be causing this?

Sent from my Galaxy Nexus using Xparent Blue Tapatalk 2
[Samsung Galaxy Nexus] MaLiXs:
i've just tried to dirty flash the rom before flash the mod and a still get bootloop

I Think im gonna go to stock rom ... getting really tired of thing like that .,... stock rom with mod that I choose ! ... with franco kernel for sure :P
[Samsung Galaxy Nexus] Misledz:
Well Dolby was placed there as it was part of the Sony XLouder series, because there was no proper way to get the sony libs to be emulated properly, the Dolby apk was placed there to fake that. Previously I had the APK placed in but the Xperia Z series wasn't properly updated with 4.2.2 file system (4.2.2 only accepts libs from 4.2.2 file system) and so their system came bundled with the proper libDolby-dsp.so

which can be found in the system/lib folder in which I had added to properly boost the system.

I can't do that you see, as if I give it to you, then the others would find it unfair and most of them would mirror it elsewhere which can be a problem since I'm trying to avoid that. my best solution would be to stay on a ROM where it would work and be stable. Just be patient, i'll be perfecting it by Friday. The audio commit CM messed up was fixed in their latest nightly so it should work.

Have you tried the flashing method I linked in my semi speech? http://xdaforums.com/showpost.php?p=43105677&postcount=2472

The idea is flash a version where the MOD worked, then dirty flash the new version with the mod and it should boot up.

Just flash the version of the ROM where the MOD worked buddy, followed by gapps, and all that (Fresh install), then dirty flash the new version of the ROM, with the MOD only, add a kernel if you want too. No need to wipe cache as the MOD does that automatically.

Follow the post above ^

I'll post a Purity screenshot later (I think that's what you're using)
[Samsung Galaxy Nexus] MaLiXs:
I'll look at it but for now i'm about to return to stock Yakju !
[Samsung Galaxy Nexus] Misledz:
Not a single loop was given. Rom, gapps, mod. Boom.

And now with Franco 382, srs how are you guys looping?
[Samsung Galaxy Nexus] greyhd:
I'm on cm 10.1 and didn't get a loop. What I did was flash the Rom and gapps then reboot. After setting up the phone I flash thus mod and reboot with no bootloop.
[Samsung Galaxy Nexus] MaLiXs:
why everytime my device go in bootloop ... what i do wrong ? :confused:
[Samsung Galaxy Nexus] Misledz:
Yeah the latest cm has the commit fixed, the other roms have yet to follow :highfive:

Like I said, again and again, just flash the version that the mod worked on (I used 5.4 since it worked fine for me), then gapps, then mod, then boot and let it create cache and dalvik, then reboot to recovery, then flash the 5.7, gapps, mod. Voila. Enjoy :good: If you do exactly as I typed then you will boot normally.
[Samsung Galaxy Nexus] xlinkprince:
Downloading....
[Samsung Galaxy Nexus] MaLiXs:
perhaps I'll try in few day if I miss purity :P

anyway thank for this answear

edit : WHAT ... look like more few minute !!! Cant live without 180 screen rotation ! I'll download previous build right now !

edit#2 : well it look like i cant find previous build on purity op ....

edit#3 : ITS ALIVE ! and I have the mod installed ! many thank to your patience misledz !
[Samsung Galaxy Nexus] Prasad:
What theme is that, Misledz?
[Samsung Galaxy Nexus] volcalstone:
[MENTION=4118822]Misledz[/MENTION] Thanks for your reply earlier. I will give it a try even though I just got done setting up my liquid rom. All I know is that I won't be clean flashing again for a while after this. Hehe. Well I'm sure it's a rom issue and nothing to do with your awesome mod.
[Samsung Galaxy Nexus] Misledz:
It's BreezeHD

https://play.google.com/store/apps/details?id=com.breezehd.theme.breezehd&hl=en

Let me know how it all turns out buddy :) :good:
[Samsung Galaxy Nexus] xxSAKISxx:
Sry guys about this question. I know that have answered before but even i follow this thread i don't remember. There is a file somewhere (after flash this mod) that can tell what mod are we have installed? If yes in what path is it?

PEACE.....
[Samsung Galaxy Nexus] Misledz:
System/etc nexuslouder
[Samsung Galaxy Nexus] Mylenthes:
I'm using the latest eos nightly 180 and after installing the mod my bass seems to be unable to be edited. Its very low and raising it in the eizo eq doesn't seem to make a difference, putting on psychoacoustic doesn't seem to make a difference.

As for hearing the bass, I have one flac album and the bass is more noticable, but all my mp3 320 albums the bass is unnoticeable. I was wondering, if I uploaded a flac album to Google music, would the quality still be better than mp3 even when streaming?
[Samsung Galaxy Nexus] Mevordel:
Google converts all of your music to mp3 when uploading, so no.
[Samsung Galaxy Nexus] volcalstone:
[MENTION=4118822]Misledz[/MENTION] Yeah it works! Did your method that you had mentioned. I'm the type that don't like to dirty flash but for your mod alone I would just for a temp fix. I'm sure this whole issue will be fix in the future with the roms.

How is that Purity rom going for you? Haven't tried it yet being a big liquid fan.
[Samsung Galaxy Nexus] Mylenthes:
Stupid galaxy nexus no SD card. Could I possibly use another app, like drop box and integrate it into a music player?
[Samsung Galaxy Nexus] Mylenthes:
My bass somehow fixed. Idk how maybe my ears weren't working yesterday. Also downloaded flac album to compare directly with mp3 and heard no difference.
[Samsung Galaxy Nexus] daniil1410:
Is the last beta safe? It won't ruin my speaker and headphones? It seems too loud. It's not that I don't like it but I hope that its safe.
[Samsung Galaxy Nexus] greyhd:
The latest is safe but it's giving some people A bootloop.
[Samsung Galaxy Nexus] daniil1410:
I just flashed and it works. Hope it will continue to work.
[Samsung Galaxy Nexus] volcalstone:
I believe it will still work as long as you dirty flash your ROM then this mod at the same time. This is gonna be the case until there a universal fix from either the ROM or this mod.
[Samsung Galaxy Nexus] Ci-Fi:
Whenever I flash this awesome MOD, my LCD density returns to the default value. If it's not too much of an endeavor, can you please retain the LCD density? Thanks.
[Samsung Galaxy Nexus] osm0sis:
Might be something to do with the build.prop tweaks but it just adds them on the end so I don't know why that would happen.. :confused:
[Samsung Galaxy Nexus] Misledz:
Well that's odd o_o The LCD density stays the same for me. What rom are you on buddy? :confused: also the MOD doesn't really touch anything density based, most of it is the audio aspect
[Samsung Galaxy Nexus] ciccionicosia:
Hi..

I have liquidsmooth 2.8 with fancy kernel 33 ext .. When i flash this mod my device go in bootloop..

before I had the rom carbon with the same kernel and it worked perfectly..

I have done all wipe, after I flashed the liquidsmooth, the gapps and the kernel .. I rebooted and i customized the ROM..after I rebooted again into recovery .. I did wipe cache and Dalvik cache and then the v7beta5 ..

Where did I go wrong?

Sorry for bad english but i am italian and thanks in advance :(

Inviato dal mio Galaxy Nexus con Tapatalk 2
[Samsung Galaxy Nexus] Ci-Fi:
I'm on CarbonRom nightlies. More info is in my signature.
[Samsung Galaxy Nexus] AspenSTi:
Soo need this on the gs4... Only had it a couple days and already missing the deep bass.
[Samsung Galaxy Nexus] itasoulas:
mod now works on latest BS 1.261 by sykomaniac! Just for the record.
[Samsung Galaxy Nexus] Misledz:
Have you tried swapping kernels bro? Anarkia mentioned he messed the recent releases, I tried on franco and nothing happened :confused:
[Samsung Galaxy Nexus] Sheetzie03:
I still have to do this method given by [MENTION=4118822]Misledz[/MENTION]

Where we flash ROM version that it works with.

Reboot Recovery. Dirty flash newest ROM version(7-1) then flash xlouder mod.

This is the only way I can get it to work work with latest beanstalk 7-1. Can you clarify this is what you mean please? Thank you.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] Misledz:
Im surprised they havent updated with the commit fix :cyclops:
[Samsung Galaxy Nexus] SahilC:
I searched, and some people are saying this mod works on Purity, some say it doesn't. Does it?

Gonna flash it now anyways :P

---------- Post added at 07:25 AM ---------- Previous post was at 06:34 AM ----------

Hey Misledz! sorry if this has already been reported,

but I flashed the latest file, and in TWRP it said "failed" and then I got stuck in a boot loop.
[Samsung Galaxy Nexus] Misledz:
Purity hasn't updated with the latest commit fix so it won't work. Their 5.7 needs to be updated, only way to get it to work is the dirty flash method from an older version.
[Samsung Galaxy Nexus] AbhishekS:
[MENTION=4118822]Misledz[/MENTION]: I have a doubt. When Purity releases 5.8 with the commit fix, will dirty flashing it solve the issue or we need to clean flash 5.8?

I got this doubt because when dirty flashing allows the mod to keep working, a dirty flash may even prevent you from installing if dirty flashing over the rom without that commit fix.
[Samsung Galaxy Nexus] Misledz:
Nah the clean flash allows you to boot normally. Carbon and some of the ROM's have done the update already and a clean wipe and flash doesn't throw you into a bootloop :good:
[Samsung Galaxy Nexus] AbhishekS:
No, you got me wrong. Or maybe I didn't put up my question correctly.

I'm asking that if I'm on a version which isn't working with this mod. And then the ROM's dev corrects it and I DIRTY FLASH the ROM. Will dirty flashing still cause bootloops or will I need to clean flash?

I have this doubt because when dirty flashing over an older build of the ROM, the mod can be installed. Is the same applicable to dirty flashing the upcoming build over the current build of the ROM where the current build hasn't fixed the commits?
[Samsung Galaxy Nexus] osm0sis:
It doesn't really make sense to me why it works either, but hey, the proof is in the pudding. ;)
[Samsung Galaxy Nexus] Misledz:
I'm not sure about that either buddy. If there is a way to check what file doesn't get replaced when dirty flashing it would help trace it down. I suppose it's best to keep the old version just in case. Just like osm0sis mentioned, we're not sure either. As long as it works that saves the whole thing
[Samsung Galaxy Nexus] :
My first thought was:
[Samsung Galaxy Nexus] Misledz:
LOL I actually had the same thing in mind, I forgot a meme existed for that!
[Samsung Galaxy Nexus] Mevordel:
To compound the confusion:

I made a script (https://github.com/Mevordel/mevmod) a while back to avoid flashing 5/6 zips every time I switched ROMs, and in it I integrated the NexusLouder patch. But when I clean flash Purity 5.7 and the zip that script generates I do not get a boot loop.

So maybe the problem has to do with how your updater-script works or something.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] AbhishekS:
So basically by integrating the mod in the ROM zip you didn't get a bootloop.
[Samsung Galaxy Nexus] Misledz:
I'll take a look at it, I learn a thing or two everyday 8)
[Samsung Galaxy Nexus] kaluoshi:
no problem here Misledz, flashing B5 worked as always (AOSPA). Should i try Revert too?

Sent using XDA Premium
[Samsung Galaxy Nexus] Mevordel:
Well, not the ROM zip, but another combo one I flash on top.
[Samsung Galaxy Nexus] Misledz:
It should work properly now :) Thanks amico
[Samsung Galaxy Nexus] kaluoshi:
Great, no problem kaibigan :D
[Samsung Galaxy Nexus] legenett:
Awsome!!!

Thank you so much! ;)
[Samsung Galaxy Nexus] AbhishekS:
So is the problem solved for those ROMs giving a bootloop?

I just flashed B5 and was still getting bootloops.
[Samsung Galaxy Nexus] Misledz:
If you're still using purity 5.7 and saying that then you haven't been reading bro..
[Samsung Galaxy Nexus] AbhishekS:
No, I'm using LiquidSmooth.

This post is the one due to which I thought you have released a fix.

---------- Post added at 04:17 PM ---------- Previous post was at 04:12 PM ----------

No, I'm using LiquidSmooth.

This post is the one due to which I thought you have released a fix.
[Samsung Galaxy Nexus] Misledz:
Then it's as simple as liquid smooth hasn't updated their rom with the commit fix. Normally cm team releases a nightly every now and then, most of it are automatically generated based on the commits done. This is however hard for most developers and so they wait for a week or two to make sure the changelog is pretty huge to avoid back and forth issues. Nothing is wrong with the mod. It works fine as far as its universal state is concerned
[Samsung Galaxy Nexus] god.fsl:
not working on slimbean 6.9 with fancy kernel r33!!!:confused:

when flash it , rom not load and got stock in boot!!!:(

sry for poor english:(
[Samsung Galaxy Nexus] :
Please read the last few posts.

Wait until the rom gets a update then try it again.

It's to complicated to understand the problem behind it

Edit:

can you boot?
[Samsung Galaxy Nexus] AbhishekS:
Wait for the ROM to be updated. It's a bug in the ROM, not this mod.

If you can't wait, flash the older version of the ROM and use this mod until the ROM dev fixes it.

But if wanna use the latest build of the ROM and the mod too, then clean flash the old version of the ROM and dirty flash the new ROM (Slimbean 6.9 in your case).
[Samsung Galaxy Nexus] osm0sis:
And so the pupil becomes the master. :D