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

Root [Virgin Mobile] [VMOBI][ROM][KERNEL] Victorious ROM + VaeVictus OC kernel (Updated 7-30-13)

FWIW, stock with Vae kernel performs almost as well as Victorious, you just have to wipe the bloat yourself with Ti, and you miss out on the swap and build.prop tweaks. Only benched a couple hundred points lower than Jerry running that setup. More effort, but the main point is even if you don't use his ROM, use Jerry's kernel. It's golden.
 
I use vae kernal plus scripts tweaks and sd swap from victorious. Post 761 (I think) in this thread. #4 and 5 in components. Works great.
 
so im haveing 2 problems ive found since flashing with this.

1. swift key wont download the language pack, which ive never had a problem doing before. it gets to around %70 then comes up with a message, and ive also connected to wifi and it says the same thing...
"network error - could not download language pack. ensure that you have a data connection available (preferably wifi) in order to continue. you may need to try again later...."
its given me this message for a few days now but i have no problem down loading apps

2. i cant veiw my gallery, sais "there is not enough space (175mb) in your device memory. delete some files"
i have maybe 20 pics and maybe 5 apps (other than system apps) and ive deleted all the bloatware....do i just need a bigger sd card??

also now that i think of it. it wasnt letting me down load pics from like google. i select the pic, puch the menu button, click download and it minimizes like normal but then just doesnt download, doesnt show anything in the top bar either as if it were to download.
 
so im haveing 2 problems ive found since flashing with this.

1. swift key wont download the language pack, which ive never had a problem doing before. it gets to around %70 then comes up with a message, and ive also connected to wifi and it says the same thing...
"network error - could not download language pack. ensure that you have a data connection available (preferably wifi) in order to continue. you may need to try again later...."
its given me this message for a few days now but i have no problem down loading apps

2. i cant veiw my gallery, sais "there is not enough space (175mb) in your device memory. delete some files"
i have maybe 20 pics and maybe 5 apps (other than system apps) and ive deleted all the bloatware....do i just need a bigger sd card??

also now that i think of it. it wasnt letting me down load pics from like google. i select the pic, puch the menu button, click download and it minimizes like normal but then just doesnt download, doesnt show anything in the top bar either as if it were to download.

How much space do that ou have on your actual sd?
 
Just wanted to say thanks for all the effort. This was my first root and it's been smooth. I did run into a couple issues. Maybe someone can tell me where I went wrong.

1. Installing apk gives me the parsing error. I do have it checked so that I can install from unknown sources. I was attempting to install fdroid and adaway.
uploadfromtaptalk1378576349278.jpg
uploadfromtaptalk1378576384708.jpg

2. Link2SD seems wonky to me. Maybe I still haven't wrapped my head around it. I found what looks like an error below.
uploadfromtaptalk1378576561190.jpg
uploadfromtaptalk1378576577896.jpg

From my understanding apps2sd doesn't work on the Victory. I don't think I have any apps2sd app installed. My links2sd shows it flip flopped, but I think things I download try to go to the internal storage and then I get low memory errors. Could someone help me with the light switch of understanding?

Thanks!
 
Excuse me if this has already been addressed but, my video player won't work. I believe that it worked before I went to cm10 but when I restored (for camera), video won't work. It's an online video that redirects to the video player app where it says that it was unable to be played. Thanks for anyone's help!
 
Thanks for this ROM and root. I just got a Victory from VM on Friday. Did the root in another thread (used TWRP 2.5.0), updated the baseband and then installed this rom. All went smooth except the TrevE tether app crashed the phone requiring a battery pull to recover. I uninstalled the app, downloaded the latest .apk (3.2-beta2-041713 **synergized**), and now that works.

What does not work, or rather what I need to understand better, is notifications.

When I get a voicemail I see it on the "swipe" screen, but if I swipe but do NOT check voice mail, the notification vanishes. Is there a way to change the behavior so that a voicemail notification remains until I actually check voice mail?

Also is there a way to put the .apk for visual voicemail back onto the phone?

I really like this ROM. Thanks for all the work and support.
 
FWIW I installed this apk and it seems to be working, at least for the time being.

hxxp://www25.zippyshare.com/d/93670654/705181/com.coremobility.app.vnotes-1.apk
 
Know I'm probably going to catch flack for this, but it possible to update the bug list? I know bugs have been reported in recent posts and it would be nice to have them all in one place.

Also, on a side note: JerryScript could you update the thread title and changelog to reflect the current release? I didn't even know there was a new release until I looked at the first post again.
 
Can't seem to disable the boot animation according to instructions, every time I try to save the edited build.prop file it fails to save no matter what text editor I use, what to do?


EDIT: Also can't seem to boot back into Teamwin to restore to recovery made before flashing ROM
 
Can't seem to disable the boot animation according to instructions, every time I try to save the edited build.prop file it fails to save no matter what text editor I use, what to do?


EDIT: Also can't seem to boot back into Teamwin to restore to recovery made before flashing ROM

Try rom toolbox in playstore. It has a buildprop editor. Twrp, with power off hold volume up and power. But rom toolbox also has a rebooter in it that lets you reboot into recovery from the app. I use it all the time. You can even add rebooter as a widget. When you first launch rom toolbox it will ask you what recovery you have, obviously choose TWRP. :D
 
It used to do that to me a little. Doesn't any more. Sometimes when it froze I would just give it a minute and it would do a soft reboot and be fine.

This is happening to me now. I had the vaevictus kernel and tried installing victorious. It will boot up, then after a very short amount of time freeze, reboot, and repeat the process. I tried waiting it out and left it charging all night. I woke up and it was still doing it..do I have to go bavk to the stock kernel
 
This is happening to me now. I had the vaevictus kernel and tried installing victorious. It will boot up, then after a very short amount of time freeze, reboot, and repeat the process. I tried waiting it out and left it charging all night. I woke up and it was still doing it..do I have to go bavk to the stock kernel

Try backing down your cpu a little. Victorious is set to max cpu, 1.8 ghz right from the start.
 
So...download no frills, and cap it under 1.2?

I keep it around 1.5 but you can raise it up. Some of our victories just dont like 1.8 right out of the gate. (Some don't like it at all.)
I use rom toolbox, has a lot more stuff in it, has a root browser and a rebooter that has reboot to recovery so you dont have to shut down to boot twrp. You can also set rebooter as a widget.
 
You can use no frills, but it doesn't display properly. I've used the cpu control in rom toolbox and it has worked great for me. Also, 1.5 is probably the best balance between performance and stability and I've not noticed much of a difference on battery life.
 
What about for the minimum cpu setting? I've experimented with 384 and 810 and still get some lag either way. As for governors, what works best? I've tried ondemand, conservative, powersave, and most recently lagfree.

I also have another issue that pops up frequently, and has done so ever since I started messing around with Victorious and VaeVictus. Pretty much every time I reboot, the battery drains quickly if I do nothing. I can go to the battery settings and almost invariably see that Media is using more power than anything else except possibly screen. But sometimes it will be using more than screen too. I don't recall ever seeing this being a power suck before I went to Victorious. However, if I tap on Media in the battery settings and kill it right after a reboot, perhaps a second time a few minutes later, everything is fine and the phone has excellent battery life. Some days, after 16-18 hours of modest usage, I will still be well above 50%. But if I don't kill Medai after booting, the power will drop 10-20% and hour or so, even if I am not using the phone at all. Any ideas about this? Has anyone else experienced this.

BTW, currently running Victorious 0.2.2 and VaeVictus 0.1.5

Everything else is awesome and I haven't had any battery overheating issues since the initial trouble I had with that shortly after flashing VaeVictus.
 
1st off, thank you to all the Developers. This is the easiest phone ever to root and customize compared to my old phone which is a HTC Wildfire S Marvelc. Anyway, I stuck with the stock 4.1 but flashed the latest kernel from Jerry Script (Thanks bro). I deleted all the bloatware and now when I make backups using TWRP 2.4 the size is only around 597mb vice 795/800. I converted most Google Apps to User Apps and uninstalled some too. What I did for Google Apps that are still system apps & have updates I will update through Playstore, backup the updated App (Es Explorer's App Manager or go to /data/apps and copy the app) which will be under User Apps, uninstall the updated App, (make sure to rename the Backed up App to the corresponding name in System Apps), finally I go the extsdcard/backups/apps and copy the app I backed up, navigate to System Apps & Paste and make sure you select overwrite so the permissions will be correct (rw r r) but always check the permissions afterwards just to be sure. Yeah you right! Thanks again and I am really enjoying this awesome phone.

P.S. Anytime I make the above mods I always reboot into Recovery using TWRP Manager by jmz and Wipe Cache & Dalvik Cache. TWRP Manager App is like having TWRP Recovery on the System.

BadbrainsEddie
New Orleans, LA
 
Use TWRP Manager App by jmz you can make Backups with the App (It's like having TWRP Recovery as an Application).

BadbrainsEddie
New Orleans, LA
 
I'm fairly new to this whole thing, only rooted a few phones and I've only ever used one custom ROM (CM for my One V)

I understand the guide says it will take a long time for it to boot, but how long should I wait before I can assume something's gone wrong? It's been at the half VM/half victorious screen for >1.5 hours and nothing has happened. I'm assuming since no one else has said anything about an extremely long boot time, that something has gone wrong, any input would be appreciated.
 
Back
Top Bottom