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

Root [Boost Mobile] A few questions...

drewhill77

Android Enthusiast
This is what I've got so far...
Stock B08c
Rooted
CWM
Superuser
BusyBox
scriptmanager
build.prop tweaks
init.d support
autozipalign
v6 supercharger - balanced 3
Auntie Dot boot animation (no sound)
Hi Launcher - Science Theme
Magic Locker - Fingerprint Scanner

todo -
loopy smoothness
move launcher into /system/app
???

Here are my Questions -
1. In your opinion what is the best setting for v6 and why?
2. When I install Loopy Smoothness should I point it at both Hi Launcher and Magic Launcher?
3. What other apps do you recommend Loopy Smoothness being pointed at?
4. Can I replace launcher2.apk in /system/app with my other launcher directly from root explorer or does that have to be done at the rom level then flashed?
5. Since Magic Locker is recognized as a launcher as well should I set it as launcher2 and then have it point to Hi Launcher?
6. Superphone I/II build.prop...worth it?
7. Any other suggestions?

Thanks in Advance...Drew
 
...Here are my Questions -
1. In your opinion what is the best setting for v6 and why?
2. When I install Loopy Smoothness should I point it at both Hi Launcher and Magic Launcher?
3. What other apps do you recommend Loopy Smoothness being pointed at?
4. Can I replace launcher2.apk in /system/app with my other launcher directly from root explorer or does that have to be done at the rom level then flashed?
5. Since Magic Locker is recognized as a launcher as well should I set it as launcher2 and then have it point to Hi Launcher?
6. Superphone I/II build.prop...worth it?
7. Any other suggestions?

Thanks in Advance...Drew

To answer some of your questions:

2: I don't believe you can point Loopy Smoothness at two different launchers, but i could be wrong. Shinru would be the guy to ask on that.

4: I've done it both ways.

6: Yes. Really, yes. YES. lol but seriously, yes, it's definitely worth it in my opinion. Makes a noticeable difference in the phone's responsiveness.

7: You may want to consider deodexing, adding the CPU thottling fix found here in the forums and maybe even adding init.d support along with Bash and Nano. You could implement some of the build.prop tweaks found here and here, if you haven't found these already. Also, you may want to consider using B08 as your start point instead of B08c. Many users report B08 has slightly louder volume, and I believe I read somewhere here that ZTE/Boost rolled back the B08c update, making B08 the official current firmware. And you could always use ABSM to add a custom boot screen! (Insert shameless self-promotion here :p)

There you go, JMTC :)
 
Thanks for the info mercury0x000d. I debated on deodexing but opted not to in the interest of speed. I've installed the throttlefix and updated to superphone II build.prop. As far as loopysmoothness and swapping launcher2...I was thinking I'd put magiclocker in the launcher2 slot and leave hi launcher in /data/app point loopy at at hi launcher as launcher and magiclocker as an app. I've already enabled init.d support...do you mean adding bash and nano support within init.d?
 
Thanks for the info mercury0x000d. I debated on deodexing but opted not to in the interest of speed. I've installed the throttlefix and updated to superphone II build.prop. As far as loopysmoothness and swapping launcher2...I was thinking I'd put magiclocker in the launcher2 slot and leave hi launcher in /data/app point loopy at at hi launcher as launcher and magiclocker as an app. I've already enabled init.d support...do you mean adding bash and nano support within init.d?

No problem! :)

From what I've observed, the loss of speed due to deodexing is negligible, and helps to cut down on the size of the ROM and makes it more easily themed. It's your ROM and therefore the choice is yours, but I always lean in favor of it personally.

So far as adding Bash and Nano, I'm talking about using dsixda's Android Kitchen to do so, however they aren't absolutely necessary, depending on your target audience. If you want to make life better for the power users out there, you could include them. Otherwise it's not that big a deal in my opinion.

Is /meta-inf supposed to disappear after installing throttlefix and init.d?

I'm not sure, but I wouldn't imagine so. Are you talking about the /meta-inf in your ROM's working folder, or on the actual phone after the ROM is installed?
 
In order to install init.d i had to unzip and manually place /meta-inf and /system in root... I know it worked because the appropriate test file was where it was supposed to be but now /meta-inf is gone. Thus far I haven't been using android kitchen... all these mods have been on the phone directly.

As far as target audience goes... I don't have one lol. I'm simply modding and customizing the phone to my liking ;). I'll put up some pics when I'm done along with a list of mods/tweaks... and if anybody wants it all put the rom up.

I'm debating on dropping back to b08 for my base... if so I wanted to Android kitchen and deodex the apks.
 
Thus far I haven't been using android kitchen... all these mods have been on the phone directly.

On the phone directly?? :eek: Impressive :)
The Android Kitchen allows you to add and modify many aspects of your ROM. Since discovering it, I've been reccommending it to like every ROM maker. Here's a link to the latest (and last, sadly) version:

https://www.dropbox.com/s/ewwwq4lkeic2az4/dsixda_Android_Kitchen_0.199.7z


As far as target audience goes... I don't have one lol. I'm simply modding and customizing the phone to my liking ;).

That's the best way to do it :)


I'm debating on dropping back to b08 for my base... if so I wanted to Android kitchen and deodex the apks.

If this helps, here's a link to a starting ROM I threw together for you. It's a stock B08 ROM already zipaligned, deodexed and has init.d support added. Note that it is completely stock, so you will have to root it and take things from there if you use it.

https://www.dropbox.com/s/d883mass1bojotm/stock_b08_deodex_zipalign_init.d.zip
 
In order to install init.d i had to unzip and manually place /meta-inf and /system in root... I know it worked because the appropriate test file was where it was supposed to be but now /meta-inf is gone. Thus far I haven't been using android kitchen... all these mods have been on the phone directly.

As far as target audience goes... I don't have one lol. I'm simply modding and customizing the phone to my liking ;). I'll put up some pics when I'm done along with a list of mods/tweaks... and if anybody wants it all put the rom up.

I'm debating on dropping back to b08 for my base... if so I wanted to Android kitchen and deodex the apks.

Pretty sure that /meta-inf are the zip installer scripts, right?? :confused:
 
That's right, meta-inf contains the script and script binary to do the installation, as well as some other files. I'm pretty sure this shouldn't just disappear...

Actually, probably yeah.

When you tried to place a new folder at root, it was probably seen as a new partition - bootloader can't let you do that.

I suspect that you saw a copy to the ramdisk (maybe) and that's why it disappeared.

Anyway, if installing /system files by hand, then you don't need the installer stuff.

Bear in mind, I could be following this discussion wrong, apologies for any miscommunication if so.
 
Pretty sure that /meta-inf are the zip installer scripts, right?? :confused:

Yes, Meta contains the installer scripts. There would be no reason to add this to anything unless you are making a flashable. The script itself is update-script. It wouldn't cause any harm adding this to the system folder, because nothing is triggering it. But there is no point to doing that
 
So in other words... If I have a zip that won't install from CWM just extract whats in /system to the appropriate folders and ignore /meta-inf and reboot for changes to take effect?
 
Back
Top Bottom