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

Root [Virgin Mobile] [VMOBI][DEV] Closed [07.08.2013]

Nothing working yet...
Here's the pastebin using 'monitor'

P.S. i have downloaded the repo, followed your instructions and some other info. I got a desktop but nothing else worked. I'll get a chance to try again this afternoon. The compile takes a 'minute' and well totally ROCKS my pc with lot's of 100% on all cores and 4Gb out of 6. I had a couple of hickups with fixing a Term.apk and a linker error and, updating java path 'export JAVA_HOME=/usr/lib/jvm/sun-jdk-1.6'i in envsetup.sh. To get the device files i booted into twrp and mounted the partition's then, from the '~/android/system/device/samsung/goghvmu' directory i used './extract-files.sh' after that yea, it was just a matter of breakfast and brunch. I'll give it another go later.

If there is anything else you need let me know!
 
JupiterOne said:
Nothing working yet...
Here's the pastebin using 'monitor'

P.S. i have downloaded the repo, followed your instructions and some other info. I got a desktop but nothing else worked. I'll get a chance to try again this afternoon. The compile takes a 'minute' and well totally ROCKS my pc with lot's of 100% on all cores and 4Gb out of 6. I had a couple of hickups with fixing a Term.apk and a linker error and, updating java path 'export JAVA_HOME=/usr/lib/jvm/sun-jdk-1.6'i in envsetup.sh. To get the device files i booted into twrp and mounted the partition's then, from the '~/android/system/device/samsung/goghvmu' directory i used './extract-files.sh' after that yea, it was just a matter of breakfast and brunch. I'll give it another go later.

If there is anything else you need let me know!
Click to expand...

The repo is a little out of date I need to push up! Also looks like I fixed the issue with permissions on the sound!! It's crashing out on libalsa-intf.so. I will take our stock one and add that into the load and see if that fixes sound. Thanks that helped a bunch. I will post another ROM in about an hour to test.
 
My Galaxy Victory gets stuck on the loading screen. It sat at the loading screen for 25 minutes before I force shutdown. Not sure why it won't load to the desktop.
 
jrccomputer said:
My Galaxy Victory gets stuck on the loading screen. It sat at the loading screen for 25 minutes before I force shutdown. Not sure why it won't load to the desktop.
Click to expand...
He's still developing it and there's a lot of bugs to work out yet...it's still in the "alpha" stage...he still needs some time/space to work on it
 
I know how this dev stuff works. I understand bugs, I understand the risk. I just thought I heard you guys say that the rom booted to desktop, just shocked when it did not. If you need a tester I would be honored to test.

I just make a full backup using TWRP so I can restore at anytime.
 
jrccomputer said:
I know how this dev stuff works. I understand bugs, I understand the risk. I just thought I heard you guys say that the rom booted to desktop, just shocked when it did not. If you need a tester I would be honored to test.

I just make a full backup using TWRP so I can restore at anytime.
Click to expand...

Once I get to a beta I will for hit you up. Right now there is just too many issues even for testing. I have been learning a ton more on the Samsung phone's and all the differences from Motorola, to HTC. It is been a new animal and a lot of fun. I am hoping to solve some more issues soon.
 
I'm super excited for it. There were so many roms for the evo that I just stayed stock. The biggest reasons I'm looking forward to it on this are my issues with the auto brightness and every time I pay a full screen game while listening to music, the music will play out the external speaker instead. So hoping a Rom will fix these minor inconveniences.
 
Tejer said:
I'm super excited for it. There were so many roms for the evo that I just stayed stock. The biggest reasons I'm looking forward to it on this are my issues with the auto brightness and every time I pay a full screen game while listening to music, the music will play out the external speaker instead. So hoping a Rom will fix these minor inconveniences.
Click to expand...

That was one of the nicest reasons to own the Evo, so many great devs working on the phone. I tried all the ROM's and prefer CM to everything. Just enough options to be crazy but not overly crazy. I just could never embrace the whole Sense...Just didn't make sense :D
 
g60madman said:
That was one of the nicest reasons to own the Evo, so many great devs working on the phone. I tried all the ROM's and prefer CM to everything. Just enough options to be crazy but not overly crazy. I just could never embrace the whole Sense...Just didn't make sense :D
Click to expand...

I couldn't stand Sense. It was extra bloat that probably bogged down the system terribly. Cyanogenmod is my favorite Rom by far. I was done with Sense based roms and the senseless ones had issues from removing certain files usually. I seriously believe the Victory is the best Virgin phone I've owned so far and the optimus v or optimus elite comes next imo.
 
My fiancee has the elite. She has for...a year and a half now? (Too long for me to keep a phone ;))

She loves it though. Won't even let me root it.

Her OV I was able to root though. Because it was her first smart phone and I convinced her it would improve performance. Which it did with some CM lovin'.
 
g60madman said:
Once I get to a beta I will for hit you up. Right now there is just too many issues even for testing. I have been learning a ton more on the Samsung phone's and all the differences from Motorola, to HTC. It is been a new animal and a lot of fun. I am hoping to solve some more issues soon.
Click to expand...

Awesome. Thanks. Great work by the way. I wish we could donate to you.
 
anyone have a working tar of the stock. i tired the one google found but data fails to restore or something and i can not mount it in twrp to restore the backups i have...

managed to recovery found the tip about formatting data again...
lost 4g lte and wifi hoping to recovery them
 
Hopefully soon. I still don't have any of the radio's working (check the op). Since I have very little time, about 6 hours a week it's taking awhile to complete.
 
I'm setting up a build environment in a virtual box. The only thing I'm questioning is I have 12GB of RAM and its recommended I have 16GB. Any advice? I wanna start tinkering with ROM's. Maybe toy with your source and get working on fixing it up.
 
dibblebill said:
I'm setting up a build environment in a virtual box. The only thing I'm questioning is I have 12GB of RAM and its recommended I have 16GB. Any advice? I wanna start tinkering with ROM's. Maybe toy with your source and get working on fixing it up.
Click to expand...

That is plenty of RAM but in a VM it's going to be super slow to build. I would recommend loading up Ubuntu if you can. Also RAM is not a problem, I have 8GB myself and never dip passed 2-2.5GB. The big thing is always going to be CPU. I am currently running a dual quad core Xeon @ 25.28Ghz. It takes me about 45 minutes to build each ROM I test. If you have a slower processor expect it to take much more time. In a VM because you're eating a lot of CPU to run your Operating System, and then more CPU to run a VM I would expect 3-4 hours on the build if not longer if you are running an i7 or better.

This is the problem with development. Make a bunch of changes to the code, then build and test. Sometimes you have a winner, sometimes you have a dud and it's back to the drawing board. Again my recommendation would be running the Ubuntu straight out and then have at it. The first computer I started development on was a Dell duo core 2.1Ghz. To compile CM9 it took me around 11 hours. CPU wins this race every time. If you have more questions post away :D
 
g60madman said:
That is plenty of RAM but in a VM it's going to be super slow to build. I would recommend loading up Ubuntu if you can. Also RAM is not a problem, I have 8GB myself and never dip passed 2-2.5GB. The big thing is always going to be CPU. I am currently running a dual quad core Xeon @ 25.28Ghz. It takes me about 45 minutes to build each ROM I test. If you have a slower processor expect it to take much more time. In a VM because you're eating a lot of CPU to run your Operating System, and then more CPU to run a VM I would expect 3-4 hours on the build if not longer if you are running an i7 or better.

This is the problem with development. Make a bunch of changes to the code, then build and test. Sometimes you have a winner, sometimes you have a dud and it's back to the drawing board. Again my recommendation would be running the Ubuntu straight out and then have at it. The first computer I started development on was a Dell duo core 2.1Ghz. To compile CM9 it took me around 11 hours. CPU wins this race every time. If you have more questions post away :D
Click to expand...

I have a quad core Intel i7 at 3.06GHz... Been thinking of OC'ing to 3.7GHz.

I'll have to find a cheap second hard disk then to put Ubuntu on, as I suspect running Ubuntu off a flash or USB drive is a terrible idea. Maybe if I took apart my old external eSATA hard drive...
 
dibblebill said:
I have a quad core Intel i7 at 3.06GHz... Been thinking of OC'ing to 3.7GHz.

I'll have to find a cheap second hard disk then to put Ubuntu on, as I suspect running Ubuntu off a flash or USB drive is a terrible idea. Maybe if I took apart my old external eSATA hard drive...
Click to expand...

Yeah I would do that and dual boot. You need about 80GB for OS and development. More is always better as you can also setup cache for building so you can further speed up the build. I totally forgot about using cache, was poking around on CyangongenMod's site and set it up today. I kicked out a build in 28 minutes which is going to help in terms of testing!!

Here are the commands to setup cache

$ export USE_CCACHE=1
$ export CCACHE_DIR=/<path_of_your_choice>/.ccache
$ prebuilts/misc/linux-x86/ccache/ccache -M 50G

If you have the space google recommends 100G which is 100GB just look for the cache.
 
g60madman said:
Yeah I would do that and dual boot. You need about 80GB for OS and development. More is always better as you can also setup cache for building so you can further speed up the build. I totally forgot about using cache, was poking around on CyangongenMod's site and set it up today. I kicked out a build in 28 minutes which is going to help in terms of testing!!

Here are the commands to setup cache

$ export USE_CCACHE=1
$ export CCACHE_DIR=/<path_of_your_choice>/.ccache
$ prebuilts/misc/linux-x86/ccache/ccache -M 50G

If you have the space google recommends 100G which is 100GB just look for the cache.
Click to expand...

Haha alright. Well, I'll dismantle that disk. If it turns out to be convertible to an internal SATA drive, its 500GB so I'm not worried.
 
Tejer said:
I am curious, will Cyanogenmod support app2sd?
Click to expand...

Once I get the SD card working perfectly, and also get data working so I can download apps from the play store I can test this out. CM by default supports running apps from the SD Card. However Samsung is a little different in terms of how they manage their storage, and also how they use the hidden partitions. I would say yes but I am not 100% sure.
 
You must log in or register to reply here.
Back
Top Bottom