• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root P.A.C.MAN Update

i ran method 2. it didnt give me any error. it just ran, didnt tell me what it was writing to build.prop. just some lines about modifying it and acid mod devs.

is that how it went ramjet?
 
LakersDroid said:
i ran method 2. it didnt give me any error. it just ran, didnt tell me what it was writing to build.prop. just some lines about modifying it and acid mod devs.

is that how it went ramjet?
Click to expand...
Yup. If you want to see what the script does it's in /system/bin and I've attached the version from 2805. Looks like only buld.prop changes to me but the last three get written to a "build." file in the same directory. :confused:

I can't make sense of what Team AC!D is doing with the installation or why so I've just flashed it as documented.

Edit: Looks like I'm not the only one that's confused. :(

ramjet73
 

Attachments

ramjet73 said:
Yup. If you want to see what the script does it's in /system/bin and I've attached the version from 2805. Looks like only buld.prop changes to me but the last three get written to a "build." file in the same directory. :confused:

I can't make sense of what Team AC!D is doing with the installation or why so I've just flashed it as documented.

ramjet73
Click to expand...

This is so confusing. I just redone method two because the first time I didn't double space!
It mounted the system this time then i went ahead with
aaengine and i got the same can't create....read only system errors as in method one :confused:
 
LakersDroid said:
This is so confusing. I just redone method two because the first time I didn't double space!
It mounted the system this time then i went ahead with
aaengine and i got the same can't create....read only system errors as in method one :confused:
Click to expand...
Did you see the post I linked in the edit to my previous post?

ramjet73
 
So it AcidMOD v7 working for our phones? Was about to flash it. Also would it work with the Play Music app?
 
Kahroo said:
So it AcidMOD v7 working for our phones? Was about to flash it. Also would it work with the Play Music app?
Click to expand...
AC!D V7 seems to work but the installation process is a little complicated and confusing:

1. Take nandroid backup
2. Flash version 7 part 1 (build_2802)
3. Flash version 7 part 2 (build_2805)
4. Wipe dalvik cache
5. Fix permission in recovery
6. Reboot your phone
7. Run "aaengine" from terminal emualtor
8. Reboot your phone

It is what it is. ;)

ramjet73
 
ramjet73 said:
AC!D V7 seems to work but the installation process is a little complicated and confusing:

1. Take nandroid backup
2. Flash version 7 part 1 (build_2802)
3. Flash version 7 part 2 (build_2805)
4. Wipe dalvik cache
5. Fix permission in recovery
6. Reboot your phone
7. Run "aaengine" from terminal emualtor
8. Reboot your phone

It is what it is. ;)

ramjet73
Click to expand...

And this makes the phone much louder? Also how do I run it in terminal emulator?
 
ramjet73 said:
AC!D V7 seems to work but the installation process is a little complicated and confusing:

1. Take nandroid backup
2. Flash version 7 part 1 (build_2802)
3. Flash version 7 part 2 (build_2805)
4. Wipe dalvik cache
5. Fix permission in recovery
6. Reboot your phone
7. Run "aaengine" from terminal emualtor
8. Reboot your phone

It is what it is. ;)

ramjet73
Click to expand...

Step 5. I've never had to do that. I didn't even know there's an option in recovery to do that!

The flashing process for acid mod is definitely too confusing for the average users. It should be made simple and easy to follow.:(
 
I checked my build.prop after flashing 2802 and 2805, and I saw two instances of the exact same codes! So I think that we don't need to flash the 2802.
We just need to flash the latest 2805 and I think that would add the build.prop tweaks.
As for the "build" file being added to /system, there are lines added to it after flashing in recovery. So I think the step to run terminal emulator is only for if we get errors. Someone please correct me if I'm wrong here.

I'm not really sure why we would have to run terminal emulator, that's really beyond my comprehension. Though, the dev mentioned something about running it if getting permission errors, permission denied. etc.
 
LakersDroid said:
I checked my build.prop after flashing 2802 and 2805, and I saw two instances of the exact same codes! So I think that we don't need to flash the 2802.
We just need to flash the latest 2805 and I think that would add the build.prop tweaks.
Click to expand...
The installation instructions explicitly say to flash 2802 and then 2805.

The reason there are duplicate entries in build.prop is that both of those zip files have scripts that add entries to the build.prop file and most of those are the same. The aaengine script uses the setprop command which is why it needs to be run manually from a terminal emulator after the first boot, and at least some of its build.prop entries are not included in the original flash. And I still haven't figured out why a file called "build." is being created in the /system directory.

Seems like a lot of black magic to me. It's no wonder selkie is having some issues updating his mod to AC!D's V7. :(

ramjet73
 
ramjet73 said:
The installation instructions explicitly say to flash 2802 and then 2805.

The reason there are duplicate entries in build.prop is that both of those zip files have scripts that add entries to the build.prop file and most of those are the same. The aaengine script uses the setprop command which is why it needs to be run manually from a terminal emulator after the first boot, and at least some of its build.prop entries are not included in the original flash. And I still haven't figured out why a file called "build." is being created in the /system directory.

Seems like a lot of black magic to me. It's no wonder selkie is having some issues updating his mod to AC!D's V7. :(

ramjet73
Click to expand...
I cannot run it through terminal emulator, I always get the can't create in /system/build., read only file system errors.

Beside that not working, I do notice the change in sound quality, so at least it sounds better with this thing installed even if it's not being installed according to instructions.
 
I'm curious ramjet, did you use the 2802 AOSP3 or AOSP2?
He mentioned if 3 doesn't work then use 2.
I guess 3 isn't working for me because I can't do the terminal emulator step.
Going to try AOSP2 then see what happens at that step.
 
LakersDroid said:
I'm curious ramjet, did you use the 2802 AOSP3 or AOSP2?
He mentioned if 3 doesn't work then use 2.
I guess 3 isn't working for me because I can't do the terminal emulator step.
Going to try AOSP2 then see what happens at that step.
Click to expand...
I used AOSP3 for both versions. I went through more of the thread and there seems to be a lot of confusion, especially about the build.prop entries.

ramjet73
 
ramjet73 said:
I used AOSP3 for both versions. I went through more of the thread and there seems to be a lot of confusion, especially about the build.prop entries.

ramjet73
Click to expand...

I read about it, too. Seems like people are getting various results.

Some only have to flash the 2805 zip to get it working. Others have to flash both. Some get errors running script in terminal emulator, while others don't.

It seems to depend on what phone and rom the flasher is running. For some phones, they have to flash both to work. I think the dev said to flash both as a precautionary measure, and also to do the terminal emulator step as a precautionary measure to fix possible errors from flashing.

He just didn't explain in detail and is very vague about it.

About the build.prop entries, I flashed both 2802 and 2805 and it definitely created double entries. They're exactly the same, I checked them line by line. I don't think it cause problems to have double entries and one can delete the duplicate entries, but! it's unnecessary for me to have them.

I just say F*** it, and just flashed the 2805 without doing anything further after a clean rom install. I wiped cache+dalvik prior to flashing it. Phone booted up fine. I get the acidmod and awesome beats apps in the app drawer. Running processes show them running, I also get the dolby mobile process and musicFX process that are a few hundred kb each when I checked under Apps---> All apps

I played some music and it sounds loud and crisp compare to how it sounds without the mod installed. So it works for me that way.
 
To be honest, all I did was flash 2805 through recovery and that's it. The music sounds so much better than without the mod. This isn't to say that it wouldn't be even better if I followed all of the steps. I will probably do so next time my rom gets an update. I will flash Ac!d properly over a fresh install. But for what it's worth, it sounds fine to me after just flashing 2805....
 
I think the dev needs to make an update and just make it a single zip file to be flashed in recovery. Why must we flash two files when he could just combine them into one? He's making things too confusing and complicated for the average users.
 
I'm so tempted to get the latest 3D CDMA build. I'm sure cmbaughman will update to the Evo V one soon. But really want to see what's new in V21
 
Anyone with evo v running the evo 3d latest build? Can you test if mms works out of the box or do we need to do a fix?
 
So I updated my rom last night and flashed ac!d properly. Was curious though if terminal emulator is supposed to print anything back after you type:

mount -o rw,remount /system

There was no confirmation that I mounted the system. after typing aaengine it seemed to run fine and everything. So if the system wasn't mounted would the other command return an error? I think it all went fine, but was just curious since I saw no confirmation that the mounting was typed correctly.
 
Brian706 said:
So I updated my rom last night and flashed ac!d properly. Was curious though if terminal emulator is supposed to print anything back after you type:

mount -o rw,remount /system

There was no confirmation that I mounted the system. after typing aaengine it seemed to run fine and everything. So if the system wasn't mounted would the other command return an error? I think it all went fine, but was just curious since I saw no confirmation that the mounting was typed correctly.
Click to expand...

From what I saw on XDA thread, if you did it correctly, aaengine would run and won't give you any errors in the process. So I believe you did it correctly.
 
Brian706 said:
There was no confirmation that I mounted the system. after typing aaengine it seemed to run fine and everything. So if the system wasn't mounted would the other command return an error? I think it all went fine, but was just curious since I saw no confirmation that the mounting was typed correctly.
Click to expand...
Yes, that's correct. No news is good news. ;)

ramjet73
 
You must log in or register to reply here.
Back
Top Bottom