Root [ROM][WIP] BACKside ROM (CM7) + Green Machine Theme

[JerryScript]

My friend's wife just got an OV. I've been asked to root and rom it for her, so my plan is to put 0131 on it, for now. It's her first smartphone, and I don't think she's ready to take on potential bugs.

If you can wait till Mon or Tues, I'll have a new build up with the fix for the screen rotation freeze bug.

 

[JerryScript]

Problem is I can't uninstall ADW!!!

And I am talking about the Start up animation. The one with the Human IO and BACKside Rom shit.

I can not remove it... thats the only thing I hate about this rom now is that animation.. its not needed...

Thanks for the apology!

To be upfront about this, I work with the public on a daily basis here in Las Vegas. The one thing I do not tolerate from customers is abusive behaviour towards my employees. I would fire any employee who cursed at or in front of a customer. I explain that to customers who seem to think it's ok for them to curse at my employees. If they are reasonable and understand my position (it's like punching someone in handcuffs, the employee cannot fight back), then it's water under the bridge. If they argue with me in the least, or use another profanity, they are out the door with zero courtesy from me. I have kicked out dozens of customers, including some of the most influential people in Vegas (one in particular has a local stadium named after him, and I could care less ).

I completely accept your apology, and just ask that you keep in mind my kids sometimes read these forums, as do other children, so please remember they are here.

If you don't like my bootanimations, I am not offended. I just didn't like the stock Virgin Mobile 1st bootanimation, so I replaced it with one I made very quickly. If you would like to submit one to be used, it can be no longer than 12 images, and must be limited to raw color format (so nothing very pretty unfortunately). Post the images in a zip, or link to them here, and I'll see if they are appropriate for use in the ROM.

 

[g33kgrrl]

Hi there. I'm pleased to report that after following the stickied tutorials, I successfully rooted and flashed a ROM for the first time. Woot!!!!

I must say that, despite a couple of hiccups, I am thrilled with the results! (I'm seeing the screen issue described by others here, and a pre-flash issue with Google Maps continues.) I've left all animations on and disabled screen rotation - so far, so good.

Anyway, performance is bomb, my bluetooth headset actually works for Skype calls now, a bunch of my pet peeves with 2.2 clunkiness are gone, and I can customize to my heart's content to streamline my everyday tasks. I have a horrible memory, no sense of direction, tons of stuff to track and get done, and have moved to an unfamiliar town... so I *live* out of my phone for keeping on top of things. This update has truly been a godsend. The good folks here have helped me more than they'll ever know. You people rock!! Kind thanks to all, and JerryScript in particular, for all your hard work. I patiently and most gratefully await the next update.

And now, if you'll excuse me, I have quite a few Thanks buttons to go click.

 

[JerryScript]

Glad to hear you got it installed and running good!

What pre-flash issue do you still have with Google Maps?
Whatever it is, I'm pretty sure uninstalling updates will fix it:

Setting>>Manage Applications>>All>>Maps>>Uninstall Updates

Then reboot, open Market, and update Maps again.

 

[exProphecy]

Can we vote for LauncherPro as stock launcher? You can set much more settings concerning memory and performance under the Advanced settings whereas ADWLauncher you cannot.

OH and about the boot up animation, I noticed right before the "BackSIDE" popping up with the little android from the corner, the logo from the previous bootup is there (the one saying CM 7.2 and the big green Android). If I attempted to edit the needed files, would it be easier to just remove the "BackSIDE" with the little android from the corner and just keep it as the "original big green android with the CM7.2 on the bottom" image?

Hope that makes sense..

 

[JerryScript]

I should have a new build up sometime tonite or tomorrow with the fix for the screen freeze due to rotations, the fix for the offline-charging bug rebooting to charger mode, improvements to scrolling (on long throws), fix for the brightness button in Power Control Widget, and the return of built in bootsounds (with an easier method to disable in settings).

I know, many of you are groaning about hearing "This phone will self destruct in 5 seconds" at boot time, but this build will give you options to disable it or change it much easier (so long as I work out the last bug ).

 

[JerryScript]

Can we vote for LauncherPro as stock launcher? You can set much more settings concerning memory and performance under the Advanced settings whereas ADWLauncher you cannot.

OH and about the boot up animation, I noticed right before the "BackSIDE" popping up with the little android from the corner, the logo from the previous bootup is there (the one saying CM 7.2 and the big green Android). If I attempted to edit the needed files, would it be easier to just remove the "BackSIDE" with the little android from the corner and just keep it as the "original big green android with the CM7.2 on the bottom" image?

Hope that makes sense..

Launcher Pro is not open source, so I will not be including it in the build. ADW Launcher is open source, which is why it's included in CM.

The IHO with the green android is a single bootlogo. It is called initlogo.rle, and it can be changed/removed without issues.

The BACKside-IHO with the peeping android is the 1st bootanimation, replacing the stock VM bootanimation. It's images are located in bootimages in the ramdisk. They can be removed/changed as you like.

The final bootanimation is based on CM's opensource bootanimation binary. The images for it are in /system/media/bootanimation.zip, and can be changed without altering the ramdisk.

 

[exProphecy]

Launcher Pro is not open source, so I will not be including it in the build. ADW Launcher is open source, which is why it's included in CM.

The IHO with the green android is a single bootlogo. It is called initlogo.rle, and it can be changed/removed without issues.

The BACKside-IHO with the peeping android is the 1st bootanimation, replacing the stock VM bootanimation. It's images are located in bootimages in the ramdisk. They can be removed/changed as you like.

The final bootanimation is based on CM's opensource bootanimation binary. The images for it are in /system/media/bootanimation.zip, and can be changed without altering the ramdisk.

So if I just delete the peeping android files, would the screen just stay on the first android bootlogo?

 

[nightspd]

Did you set it to Set On Reboot? If not, and you rebooted, you'll be back to 600.

806 is a huge overclock, so you definitely should see things run smoother and somewhat faster, and if you run any benchmarks, you will definitely get better results!

Thanks Jerry. I did set it that way, rebooted, but performance was still sluggish and Quadrant was reporting a score of 682. So, I decided to go back to 01312012 build. I booted into recovery, cleared my cache and dalvik cache 3 times each, applied the ROM, did NOT apply Green Machine (wanted to try it w/o to see what it looked like), then applied gapps. Rebooted, ran for a while, then ran a new Quadrant and I got a score of 1174 and the phone FLIES, especially when browsing the web using x-scope. I didn't even apply the V6 SuperCharger this time, and it still is snappier than hell.

The one thing I've noticed is that using Swiftkey-X, it seems to really affect the performance when switching back/forth between entering text, or just moving around the device. I need to check to make sure I have the latest version, that might help.

But damn, I love this Rom. I feel like i have a completely new phone. Thank you Jerry!!

-c

 

[g33kgrrl]

Glad to hear you got it installed and running good!

What pre-flash issue do you still have with Google Maps?
Whatever it is, I'm pretty sure uninstalling updates will fix it:

Setting>>Manage Applications>>All>>Maps>>Uninstall Updates

Then reboot, open Market, and update Maps again.

Yes, very pleased - thank you! Other than a few particulars, in the end it was still very much like flashing a computer BIOS. This ROM is just full of great improvements over the stuff VM loaded us up with.

Well, at the risk of hijacking the thread... heh...

When the screen times out with Maps open, and you wake it back up, many times the map view has gone blank (white) except for the top dashboard and controls (navigation and zoom buttons, etc.). Zooming in or out doesn't help, and neither does going to list view and back to map view. Often at this point, if you're lucky, Maps will soon throw a Force Close. If you're not, you'll usually have to go kill it manually. This problem also seems to occur sometimes when you switch tasks and come back to Maps.

Thanks for being so helpful. I've tried the process you suggest, on VM stock 2.2.1. I also tried uninstalling the updates and just leaving them off. No love. Now with BACKside, it doesn't merely uninstall updates but rather uninstalls the whole program. Tried that too. In both cases I tried deleting the data and clearing the cache before I started. Lots of googling, little in the way of answers, it seems.

 

[JerryScript]

So if I just delete the peeping android files, would the screen just stay on the first android bootlogo?

Yes, but you have to delete them in the ramdisk, not in the ROM zip file, and not on your phone after install.

If you are going to the trouble of editing the ramdisk, don't just delete the files, edit init.thundrc.rc and remove the following code block:

# This does the initial RLE animation for the vendor logo.
# Taken verbatim from the stock init.rc.
service bootlogo /sbin/bootlogo
  user root
  group root
  oneshot

# * If booted via power button
on early-boot
  start bootlogo

 

[JerryScript]

Yes, very pleased - thank you! Other than a few particulars, in the end it was still very much like flashing a computer BIOS. This ROM is just full of great improvements over the stuff VM loaded us up with.

Well, at the risk of hijacking the thread... heh...

When the screen times out with Maps open, and you wake it back up, many times the map view has gone blank (white) except for the top dashboard and controls (navigation and zoom buttons, etc.). Zooming in or out doesn't help, and neither does going to list view and back to map view. Often at this point, if you're lucky, Maps will soon throw a Force Close. If you're not, you'll usually have to go kill it manually. This problem also seems to occur sometimes when you switch tasks and come back to Maps.

Thanks for being so helpful. I've tried the process you suggest, on VM stock 2.2.1. I also tried uninstalling the updates and just leaving them off. No love. Now with BACKside, it doesn't merely uninstall updates but rather uninstalls the whole program. Tried that too. In both cases I tried deleting the data and clearing the cache before I started. Lots of googling, little in the way of answers, it seems.

Sounds like a maps issue, since it's happening to you on both 2.2.1 and 2.3.7, so you might want to report it to Google Maps. They are responsive. I reported an issue with a single 1/2 mile pedestrian path not being recognized as a bike route (in Nevada, all pedestrian paths are legal for bikes and e-bikes). It took them about two weeks to respond, but they did acknowledge the issue, and about 5 months later, they emailed me to let me know the issue was resolved. Pretty good support for a single 1/2 mile stretch of trail that isn't even used that often!

Edit: Let me know if the next build (coming shortly) makes any difference. There's the possibility it is related to the screen rotation bug, which there is a fix for in the new build. Though the fact it happens on 2.2.1 makes me think it's Maps.

 

[exProphecy]

Yes, but you have to delete them in the ramdisk, not in the ROM zip file, and not on your phone after install.

If you are going to the trouble of editing the ramdisk, don't just delete the files, edit init.thundrc.rc and remove the following code block:

# This does the initial RLE animation for the vendor logo.
# Taken verbatim from the stock init.rc.
service bootlogo /sbin/bootlogo
  user root
  group root
  oneshot

# * If booted via power button
on early-boot
  start bootlogo

And I can edit init.thundrc.rc through ES File Explorer? or must the phone be off?

 

[JerryScript]

And I can edit init.thundrc.rc through ES File Explorer? or must the phone be off?

No, it's part of the ramdisk, you have to extract everything. I believe brotherswing or andy posted a link to a how-to somewhere in the last couple of pages.

 

[JerryScript]

New build is up:

BACKside-IHO-VM670-02122012.zip
md5sum 51ba91eb8237c85977877f32e3eddb99

GreenMachineTheme-02122012.zip

Changes:
- Synced with CM:
-- Fix for screen freeze bug in new rotation animations
-- Fix for brightness controls in Power Control Widget
-- Improved scrolling cache, should make long throws a bit smoother
- Bootsound is back, but this time it comes with a setting I added to Settings>>CyanogenMod settings>>Sounds>>Bootsound, so you can turn it on/off easily. Change /system/media/android_audio.mp3 to any short mp3 you like, or disable if you don't like.
- BacksideUpdater checks for network connection now, if not present, gives option to goto wireless settings
- Offline-charging fixed, reboots reboot, and crashes reboot, only power off goes to offline-charging now. You can sleep easily with your phone plugged in now, if there is some random reboot, it will reboot fully and you wont miss your alarms or phone calls.

Thanks to Blarf, BobZhome, mrg666, tdmcode, LeslieAnn, thekraven, kermikalelite, Whyzor, bigsupersquid, eollie, aosp, the cm team, and a whole lot more!

 

[G19]

Hey Jerry, why do I lose 40mb of internal storage when I update from 1/31 to 2/12? I do not use link2sd.

 

[brotherswing]

Starting with the first February build, Jerry isn't using the move dalvik trick because it was causing some people market issues.

 

[brotherswing]

Quicksilver has been updated.

 

[rooter1]

I upgraded to the latest build this morning. Lost 3G somehow along the way, and after about an hour on the newest build experienced the screen lock again. Restored a backup and all is well with 3G on a prior build. Will give it another go after a grocery suite run.

Bugs or not...as always excellent work and support by the man Jerry!

Edit: bonehead moment....Juicedefender had 3G disabled. :banghead:

 

[rooter1]

I upgraded to the latest build this morning. Lost 3G somehow along the way, and after about an hour on the newest build experienced the screen lock again. Restored a backup and all is well with 3G on a prior build. Will give it another go after a grocery suite run.

Bugs or not...as always excellent work and support by the man Jerry!

Edit: bonehead moment....Juicedefender had 3G disabled. :banghead:

Ok, wiped cache and davlik cache and reapplied update as well as green machine theme. All seems well now. :thumbup:

Oh, and for those of you that are upset about the lack of internal memory due to Jerrys rewrite (even though as he's pointed out you couldn't use most of that space anyway), between integrating sys davlik into ROM using Titanium Backup, and some linking of davlik cache files using Link2SD, I have 90MB free internal after having 60 apps installed. Just make sure you remove the integration before you upgrade again.

 

[Atma]

integrating sys davlik into ROM using Titanium Backup,

I've never been able to see any difference using the integrate dalvik option.

before integration

after integration

before integration

after integration

 

[rooter1]

Next time I will take a before shot as well, but it integrated about 10 to 15 MB into the ROM for me.

But hey, everyone is setup a little differently...part of the fun on it here for me.

 

[Atma]

Next time I will take a before shot as well, but it integrated about 10 to 15 MB into the ROM for me.

Yeah it says it is integrating 15.1 meg for me but I'm not sure what good it does.

 

[m0bstr]

i know this is a dumb question, but how do i get the homescreen to show the time up top??

 

[Atma]

i know this is a dumb question, but how do i get the homescreen to show the time up top??

Settings > CyanogenMod Settings > Interface > Status bar tweaks > scroll down to 'status bar clock', either show clock is unchecked or the color is probably set to black. Change it to something purdy.