• 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)

Would someone mind posting the deodexed s-voice apk. I'm having a bit of pc issues so I'm unable to get it at moment. Thanks in advance
 
I downloaded this ROM and decided NOT to install it, as I would like to be able to UNDERCLOCK the kernel to save power.
 
-
I downloaded this ROM and decided NOT to install it, as I would like to be able to UNDERCLOCK the kernel to save power.

While the RedSpot Uncapped kernel does not specifically underclock, it also does not spcecifically overclock, it only uncapps the clock speed limits. As you can see from CPU-Z, the range of the clock speed at the time I took this was as low as 384Mz and as high as 1.51GHz. While just sitting on the charger with the screen on and a few widgets running, it stays between 384-918MHz most of the time:
Screenshot_2013-07-04-23-47-24_zps187f0aac.png

You may chose NOT to install it, that's NOT going to hurt my feelings! :rolleyes:
 
I got this fully working in the on the Sprint. Can't connect to lte but I got 3G. Weak 3g

Try copying your lib folder from the stock Sprint 4.1.2 to your phone's lib folder, overwriting everything. Be sure to have a backup first! Reboot and see if that helps. You will probably need a few of the Sprint apps as well, but I do not touch the modem, so that should not be affected by an install of Victorious, you just need the apps and libs to properly access it.

Of course, when trying to port a ROM from one phone to another, logcat is your friend! ;)
 
And for my camera settings, if I want to store pics on my SD, (now what shows up as internal storage) what to I select to save it to? The memory card or phone?
 
-

While the RedSpot Uncapped kernel does not specifically underclock, it also does not spcecifically overclock, it only uncapps the clock speed limits. As you can see from CPU-Z, the range of the clock speed at the time I took this was as low as 384Mz and as high as 1.51GHz. While just sitting on the charger with the screen on and a few widgets running, it stays between 384-918MHz most of the time:
Screenshot_2013-07-04-23-47-24_zps187f0aac.png

You may chose NOT to install it, that's NOT going to hurt my feelings! :rolleyes:

Thanks for clearing that up Jerry! A quick question for you. Does this ROM still have the "Power Save" button? I just found it yesterday and it appears to have solved my battery problems... Woke up this morning with it at 86% without having to leave it on the umbilical cord!
 
Thanks for clearing that up Jerry! A quick question for you. Does this ROM still have the "Power Save" button? I just found it yesterday and it appears to have solved my battery problems... Woke up this morning with it at 86% without having to leave it on the umbilical cord!

Yes, it's still there, but I don't use it and haven't tested it on Victorious. I believe I've left everything in to keep it functional, but it does need testing to confirm. ;)
 
After installing the rom the wifi tether treve mod crashes when starting tethering. Is anyone else having this issue?

I think I included the wrong WiFi Tether version, try uninstalling and installing the one from the thread on tethering in this forum. I'll try to test them out this weekend and get the right apk in the next release.
 
FYI - I'm working on incorporating true apps2sd support. I had a scary but seemingly successful build last nite, but the scary issues make me want to do considerable testing before releasing it.

What happened: I added support for a2sd, which is actually built into the system just not activated in the ramdisk. I kept the extSD2internalSD mod, since the external SD is the only one you can partition. I used the SDcard I had used on my Optimus V since it was already partitioned and formatted to ext4. As soon as I booted, every app started crashing, but the system kept running fine. I looked in the app drawer, and saw a listing of the apps I had installed on the Optimus V. I then realized I had not re-formatted the SDcard from my Optimus V, so the Victory was attempting to load the apps I had installed on the OV.

This makes me believe I have it working, for the most part, since it did actually try to load the apps from the ext4 partition on the external sdcard (swapped for internal). Unfortunately, I decided to upgrade my Ubuntu install (Wubi flavor) to 12.04, which is not a stable release for building Android (still experimental). I've been able to load Ubuntu, update everything, run apt-get install to download the build requirements for Android, and actually use many of the sdk tools. I was even able to do a couple of test builds of Victorious. However, after the third or fourth boot into Ubuntu, it doesn't boot up anymore, stupid experimental branch (actually, stupid me for using an experimental branch). This has happened to me three days in a row now, wasting 4 hours each day to install and update everything, get a build done, then have Ubuntu not boot and give up for the night.

Long story short, I'm going to install Ubuntu 11 via Wubi, and see if I can get a stable build environment going. So please be patient, but keep your fingers crossed for apps2sd support soon!
 
First of all, great job with the release! I've been enjoying it so far! The only negative is that for whatever reason, my battery seems to die 3x as fast now. With me thinking like I still have my Evo 3D, I went and wiped the phone, and then installed this. So... yeah, now I'm in a world of hurt (didn't check the forums before doing it). I had two backups but they don't seem to be working at all which kind of sucks. hard.

Currently I'm downloading the stock rom. Hoping to reinstall your rom asap and in turn am hoping that it won't drain my battery again. I'll let you know how it goes.

EDIT: So I hit a brick wall, guys. I need some help because I really don't want to lose my phone (its not "bricked"). I download VMOBI's stock ROM but I installed clockworkmod (no idea when) and keeps saying MD5 mismatch when I try to restore the stock ROM. I can't access my backup that I found which is when I backed up my original ROM (virgin mobile -- untouched). Would rather have the other recovery program, but I have no idea where to find it.

3 AM crazyness is going into full swing so yeah. I need sleep. =S

EDIT 2: Lastly, Jerry. I hope you release a full version of this. I would solve another guy like myself to get out of this sort of situation easier. I know another guy whose ROM I used on my Evo 3D used the site: http://goo.im/.

EDIT 3: Made a thread for helping me with my issue, check it out if you want to help out! Thanks - http://androidforums.com/virgin-mob...lp-reinstalling-stock-vm-rom.html#post5958039
 
This phone and rom blow my old Evo out of water. With the Evo my battery would be almost dead half way through the day. With the Victory and Jerry's rom I have been no less than 40 percent at bedtime
 
Try copying your lib folder from the stock Sprint 4.1.2 to your phone's lib folder, overwriting everything. Be sure to have a backup first! Reboot and see if that helps. You will probably need a few of the Sprint apps as well, but I do not touch the modem, so that should not be affected by an install of Victorious, you just need the apps and libs to properly access it.

Of course, when trying to port a ROM from one phone to another, logcat is your friend! ;)

Could you explain or less me to a thread that explains low-fa logcat? I copied and overwrote the lib with no success. And which Sprint apps do you think I'll need?
 
Could you explain or less me to a thread that explains low-fa logcat? I copied and overwrote the lib with no success. And which Sprint apps do you think I'll need?

To pull a logcat, just hook your phone up to your computer, and run adb, then enter the following command:

adb logcat > logcat.txt

Wait 30 seconds, then press cntrl+c to stop the logcat. Find the logcat.txt file and copy and paste it's contents to pastebin.com, then post the link here for us to check out. ;)
 
First of all, great job with the release! I've been enjoying it so far! The only negative is that for whatever reason, my battery seems to die 3x as fast now. With me thinking like I still have my Evo 3D, I went and wiped the phone, and then installed this. So... yeah, now I'm in a world of hurt (didn't check the forums before doing it). I had two backups but they don't seem to be working at all which kind of sucks. hard.

Currently I'm downloading the stock rom. Hoping to reinstall your rom asap and in turn am hoping that it won't drain my battery again. I'll let you know how it goes.

EDIT: So I hit a brick wall, guys. I need some help because I really don't want to lose my phone (its not "bricked"). I download VMOBI's stock ROM but I installed clockworkmod (no idea when) and keeps saying MD5 mismatch when I try to restore the stock ROM. I can't access my backup that I found which is when I backed up my original ROM (virgin mobile -- untouched). Would rather have the other recovery program, but I have no idea where to find it.

3 AM crazyness is going into full swing so yeah. I need sleep. =S

EDIT 2: Lastly, Jerry. I hope you release a full version of this. I would solve another guy like myself to get out of this sort of situation easier. I know another guy whose ROM I used on my Evo 3D used the site: Goo.im free android file hosting.

EDIT 3: Made a thread for helping me with my issue, check it out if you want to help out! Thanks - http://androidforums.com/virgin-mob...lp-reinstalling-stock-vm-rom.html#post5958039

I answered your other thread, lets keep the discussion there so as to prevent confusion. ;)
 
Hey guys, I have been reading and rereading this forum now for a couple of hours... and i just have a couple of questions i wanted to clear up before I move forward.

1. I used TWRP to root my phone, I would like to stick with that but have no issues using odin and running CWR, but I wanted to ask aycjay95 what version TWRP did you use and how did you over come the issues with v 0.1.2.

2. Right now I do not want to use extSD2internalSD should i delete the script before and rezip the build or just delete the script after complete flash?

3. I have seen a couple mixed comments about battery life... is there a clear answer out there about this.

I want to say thanks to everyone working on this and putting your time and effort into this phone, it is a great phone not getting much attention by many Devs.
 
Hey guys, I have been reading and rereading this forum now for a couple of hours... and i just have a couple of questions i wanted to clear up before I move forward.

1. I used TWRP to root my phone, I would like to stick with that but have no issues using odin and running CWR, but I wanted to ask aycjay95 what version TWRP did you use and how did you over come the issues with v 0.1.2.

2. Right now I do not want to use extSD2internalSD should i delete the script before and rezip the build or just delete the script after complete flash?

3. I have seen a couple mixed comments about battery life... is there a clear answer out there about this.

I want to say thanks to everyone working on this and putting your time and effort into this phone, it is a great phone not getting much attention by many Devs.

First, go into TWRP and make a backup. Then if you do install CWM, make a backup in CWM. Copy those backups to your PC. Best to be safe, especially when you are doing something unfamiliar!

  1. AFAIK TWRP 2.4.3.0 works fine for installing Victorious, I'm just used to CWM, been using and building it from source for years now (will be building my own custom recovery for the Victory soon)
  2. You can delete the file /etc/init.d/11extsd2internalsd and you will be back to normal. However, future releases of Victorious will incorporate apps2sd support, which requires a second partition on the sdcard used to store the apps, and I don't think anyone wants to mess around with partitioning the internalsd at this point, so ext2internal will be needed.
  3. I used my phone pretty heavy today! I got up and took my phone off the charger today at 7am, it's 9:48pm now and I still have 42% battery. During that time I made more than a dozen phone calls, played some games (<45mins total), sent/received several sms and mms, took several pictures and videos, backed up everything with TitaniumBackup, borked my phone attempting to use the hidden menus via phone dialer (don't use them on Victorious!), restored the stock rom, rebooted and reactivated my phone, tested with a couple of calls, installed Victorious-0.1.2 and then tested phone, sms, mms, camera, video, browser and other apps, re-logged into accounts and set them up, redownloaded several apps from the Play Store, restored all my other apps with TitaniumBackup, re-set my home screens, and finally booted into recovery to make a new backup. I do use the connections optimizer, I do not use the battery savings features in settings (others do and swear by them). Not bad battery life if I can do all that and still be at 42% 14 hours later IMHO. ;)
 
Cool
one other question concerning ext2internal.... how will the phone act if i have no SD card installed at the moment and then plan to add a 32gb or 64gb later... will current installed apps function /new installed apps?

and DAMN on that battery... sounds convincing enough for me...

one last question i just got my phone today and my first experience with VM, it is activated now... will flashing this upate require me to reactive and is that pretty easy
 
I normally don't cross post but the other place I posted this comments only has posts by JerryScript and I.

I've been running since Friday with absolutely no real problems. The only thing I noticed is System Update in settings does not work.

Also, not a problem but a request that may be more than what should be done with this ROM. I would like to be able to change the toggles on the status bar.
 
Back
Top Bottom