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

Root [ROM] Starship Triumph - The Final Voyage - (7.31.2012)

Sorry have had CM7.2.0 on my phone so have not tried to reproduce. The only difference between those different versions is a, I forgot to change the version number in about phone when I rebuilt with the updated Play Store App and Play Music app name so it copies over the Stock player so I fixed this in 1.7.5 & 1.7.6 and then cleaned up spelling errors on my part and a few other little things along the same lines that just bothered me and wanted to correct if I am not going to update for a bit. Did not say anything because I didn't want people to think they needed to flash again as the differences are minor and not worth the trouble. Otherwise I did see the torch issue in one of my test flashes after I edited the torch images a few builds back coming from a build with the old images. I cleared the app data in application settings and gave both caches another wipe in recovery and it was OK. This may be a larger issue though with the statusbar but would still give it a try.
 
  • Like
Reactions: SyberTiger
Upvote 0
I cleared the app data in application settings and gave both caches another wipe in recovery and it was OK. This may be a larger issue though with the statusbar but would still give it a try.

Clearing the app data, specifically for Torch, did not fix the Torch issue I reported. However, wiping the cache then wiping the Davlik cache did in fact fix the problems I reported for the WiFi, GPS, and Torch widgets buttons. They now behave properly. What is weird is that I had performed the following installation process with the latest build but that is what left me with the reported problems:

Chairshot215 said:
1, Boot into Recovery.
2, select "wipe cache"
3, Under Mounts and storage select "format /system".
4, under advanced select "wipe Dalvik cache"
5, select "install zip from sdcard"
6, select "choose zip from sdcard"
7, select "Starship_Triumph.zip" from the available list of files.
8, select "yes install Starship_Triumph.zip"
9, select "choose zip from sdcard"
10, select "Whatever Gapps you are using.zip" from the available list of files.
11, select “Whatever Gapps you are using.zip "
12, Reboot.

This may mean that after a new ROM flash you need to redo steps [2] and [4] again. Is it possible your build contains residual data leftover from your (Charishot) personal caches?
 
Upvote 0
Yah I had suspected the first part with torch was not going to help but thought the Caches would. Generally after updating if I have an issue will clear the applications data for whatever app is acting funny and then directly from the Applications settings menu will immediately reboot into recovery and wipe the caches again before e opening the app. Probably extreme but will also power down from recovery after wiping and then take the battery out for a minute or two before turning on to be sure all the old data is out of memory. For the most part one of these fixes things but do it all at once to cover all the basis.
 
Upvote 0
I loaded this yesterday and it's great...no problems so far, until I decided to play with the lock screen settings. I changed it to lense and It shows a lock in the center with down arrows on each side, but for the life of me I can't figure out how to unlock it now.


HELP!

I called myself and was able to change it back to ring, but still interested in how you unlock it from the Lense lockscreen.
 
Upvote 0
Before when gapps were included, even playstore had a very unique icon.

Think that was another Razr icon. Old music player apk was actually from the Razr also, not that there was a noticeable difference. When updating to CM7.2.0 may include an actual theme so I can do some image redirects for apps not included and put it back in.
 
Upvote 0
Just flashed this, like it already. Just wondered about the theme Chooser apk, I tried pulling it from g60's and placing it in system /app it went but not showing up, or won't install, am I missing a step? Thanks in advance

There is two parts to make it work. Try copying

ThemeChooser.apk
ThemeManager.apk

I am not 100% sure it will work but you can give it a shot.
 
  • Like
Reactions: henslo
Upvote 0
Got the Thememanager.apk to install, still can't get the Chooser to install, just says "application not installed "

Some apps don't "install" When you drop the apps in the /system/app directory they are ready. You just need to reboot and they will be reloaded with their cache wich will make the boot take a little longer. keep that in mind if you drop a bunch of app like I do. It will take longer at the bootanimation.zip.
 
  • Like
Reactions: Chairshot215
Upvote 0
Other than temporarily locking myself out, so far this is a pretty sweet ROM. I did the theme. The ReLaunch was cool, but the red was getting pretty harsh. Haven't had any other problems and the bluetooth is working flawlessly! YES!


I really need to do that Re-launch colour again some day. Have learned a few new ways of doing it since then.
 
Upvote 0
Love the ROM!
Either the release before this one or the next before that (can't remember which since I can't find older releases) was phenomenal especially the response of the four hard keys below the screen. There was no lag and the haptic feedback seemed especially strong so there was no doubt I pressed a key.

I'm having an issue though with the latest update that I always got with CM7 TGR and g60's ROM that any of the hard keys can fail to respond for quite a while. This always seemed to happen at random. The four keys' haptic feedback also seems weaker. I've tried wiping everything and reloading twice but this still happens from time to time. Could it be some of the code you added from g60's ROM may be causing this?
 
Upvote 0
I'm having an issue though with the latest update that I always got with CM7 TGR and g60's ROM that any of the hard keys can fail to respond for quite a while. This always seemed to happen at random. The four keys' haptic feedback also seems weaker. I've tried wiping everything and reloading twice but this still happens from time to time. Could it be some of the code you added from g60's ROM may be causing this?

I experience this same phenomenon also. I can't seem to reproduce it at will. It acts like the processor just gets lost doing something and it can take 30 seconds or more sometimes to snap out of it.
 
Upvote 0

BEST TECH IN 2023

We've been tracking upcoming products and ranking the best tech since 2007. Thanks for trusting our opinion: we get rewarded through affiliate links that earn us a commission and we invite you to learn more about us.

Smartphones