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

So for some reason when I take a picture it acts like it's taking it and I see the thumbnail saved in the corner. But when I try to access the photos it says memory full(16642mb free) consider deleting some files and I can't find the pictures I took anywhere. And obviously my memory isn't full there's over 16gb left on my sd card that is mounted as internal. The option to save to phone or sd doesn't help it still days memory full.. But the pictures i took didn't save and they were somewhat important.
 
OK, a couple more things to report now. I left the phone plugged in, but turned it off before going to bed because I was afraid it might get too hot without me knowing about it. I did not at any point since yesterday ever move the lower slider for the cpu below the 918 it was sitting on (I had only moved the upper down to 1512). This morning after rebooting, it was set on 384 and 1836, and constantly going to both extremes on the reading, occasionally hitting a number in the middle ground. The two screenshots below are literally 2 seconds apart. Also, with only a few minutes of use, I've lost 17% charge in the last 1 1/2 hours from a full charge. Normally, with this kind of use it would still be probably 95-96%.

2013-07-28%2008.12.58.png


2013-07-28%2008.13.00.png
 
@crshortt:
Your screen caps all look good, you have the appropriate scripts in the appropriate places. Your CPU frequency should be jumping around, that means the governor is working. If the governor wasn't working, it would stay at one frequency level all the time, or crash. You cannot determine actual battery life the first day of using a new governor. The way battery stats work is based on history, and you have to develop a new history with a governor before you get true results. That being said, dropping 17% in an hour and a half is not unusual, depending upon the background services in use at the time. Check your battery stats in settings and see what's using up your battery. Also, I have no idea if CPU Control works properly on the Victory, I suggest No-frill CPU Control in the installation instructions, and that's what I use so I can support it's use on the Victory with my experience with it (as well as duplicate what others with issues have done). If I was having your issues, I would first attempt a reflash of Victorious, and then let it run for a day to set it, and if I still had issues, I would restore the stock backup, boot it up and do all the updates in settings, then try flashing Victorious again.

I'm testing various configurations of the governors, and yesterday I tested the conservative governor with max at 1.836 and min at 384 with cfq scheduler. Here is a screencap of my results through 20 hours:
Screenshot_2013-07-28-05-21-45_zpsd55aeae5.png
 
TriumphLance said:
So for some reason when I take a picture it acts like it's taking it and I see the thumbnail saved in the corner. But when I try to access the photos it says memory full(16642mb free) consider deleting some files and I can't find the pictures I took anywhere. And obviously my memory isn't full there's over 16gb left on my sd card that is mounted as internal. The option to save to phone or sd doesn't help it still days memory full.. But the pictures i took didn't save and they were somewhat important.
Click to expand...

Did you switch your camera's storage location to phone? The phone's memory is swapped with the sdcard due to ext2internal. ;)
 
OK. Just to be clear again.

1) Based on the screen caps, you think my partitioning is fine and I don't need to reformat? I can live with that, but I still don't understand why internal sd and external sd both show the 28.7 GB card. Where is the original internal that was 1.73 GB?

2) reboot into recovery, wipe cache and dalvik cache, then reinstall Victorious

3) I just downloaded no-frills cpu control. How do I use it?

BTW, thanks so much for all your help! The same goes again to everyone else who has responded so far.
 
crshortt said:
OK. Just to be clear again.

1) Based on the screen caps, you think my partitioning is fine and I don't need to reformat? I can live with that, but I still don't understand why internal sd and external sd both show the 28.7 GB card. Where is the original internal that was 1.73 GB?

2) reboot into recovery, wipe cache and dalvik cache, then reinstall Victorious

3) I just downloaded no-frills cpu control. How do I use it?

BTW, thanks so much for all your help! The same goes again to everyone else who has responded so far.
Click to expand...

  1. The storage has been swapped, but the internal class that reads it has not been modified to read it properly, I hate mucking around in smali files. ;)
  2. Yep, a wipe and re-install is always a good first step to fixing issues
  3. Open no-frills and click on the items listed on the right, they are all drop-down menus that allow you to adjust things. I would start with max 1.5 min 384 governor conservative (or powersave) and leave the scheduler alone.
If you still have issues, then a stock restore would be the next step.
 
OK. I will try that. I don't understand what you are talking about in #1 though.
"the internal class that reads it has not been modified to read it properly, I hate mucking around in smali files."

Is that a problem with what I did, or a pre-existing problem with the firmware or Victorious. If that is something I need to live with, so be it. But if it is something I can fix without getting in over my head, I'm willing to try.
 
crshortt said:
OK. I will try that. I don't understand what you are talking about in #1 though.
"the internal class that reads it has not been modified to read it properly, I hate mucking around in smali files."

Is that a problem with what I did, or a pre-existing problem with the firmware or Victorious. If that is something I need to live with, so be it. But if it is something I can fix without getting in over my head, I'm willing to try.
Click to expand...
Live with it, it's my laziness. ;)

(or someone else could fix the smali and I'll pack it into Victorious)
 
FYI- I just posted a new kernel build with rbheromax's latest fixes to the frequency tables. Should fix stability issues some were experiencing. Donwload link is in the VaeVictus thread. ;)

Thanks again rbheromax!
 
Well almost back in business. Last night I was able to do the complete stock restore and get everything updated and back online and working.

SO now that I have updated everything, reinstalled TWRP, reinstalled root I have a bone stock Victory... and it sucks... LOL I want my victorious back... but here is what I am running into.

I partitioned my SD card using peppermint linux, I created the first partition as FAT32 @ 18GB I created the second partition ext4 @ 12GB, Once I launch Link2SD I get the following error about creating mount scripts.

"Mount script cannot be created.

mount: Invalid argument

ext4 may not be supported on your device. Try FAT32 on the second partition"

I am going to throw in good old ubuntu 12.04 and try to repartition the sd card using gparted and see if I get the same results.

Any help or ideas would be greatly appreciated.
 
Epixtruth said:
Well almost back in business. Last night I was able to do the complete stock restore and get everything updated and back online and working.

SO now that I have updated everything, reinstalled TWRP, reinstalled root I have a bone stock Victory... and it sucks... LOL I want my victorious back... but here is what I am running into.

I partitioned my SD card using peppermint linux, I created the first partition as FAT32 @ 18GB I created the second partition ext4 @ 12GB, Once I launch Link2SD I get the following error about creating mount scripts.

"Mount script cannot be created.

mount: Invalid argument

ext4 may not be supported on your device. Try FAT32 on the second partition"

I am going to throw in good old ubuntu 12.04 and try to repartition the sd card using gparted and see if I get the same results.

Any help or ideas would be greatly appreciated.
Click to expand...

Go into /system/etc/init.d and delete everything but 11extsd2internalsd and delete /system/etc/install-recovery.sh, then flash Victorious. Now when you open Links2Sd, if it asks to create mount scripts, say no. You should be good to go.
 
JerryScript said:
Go into /system/etc/init.d and delete everything but 11extsd2internalsd and delete /system/etc/install-recovery.sh, then flash Victorious. Now when you open Links2Sd, if it asks to create mount scripts, say no. You should be good to go.
Click to expand...

So its ok that it didnt create any mount scripts at this point? when I go into link2sd, storage info it shows my /storage/extSdCard as the fat32 partiton correctly but it isnt mounting the 2nd partition
 
I have reinstalled Victorious. Too soon to tell how it is going, but no issues have jumped out at me yet. I finally found my original internal sdcard0 in ES File Explorer (it was not at all obvious), after first finding it using the Root Browser in ROM Toolbox, where it was very obvious. What do I need to do to deal with those files? Should they be copied to the "new" internal sd now, since that is where they originally were? Or do they need to stay there, be deleted unless they contain personal files? Not sure what their status is. Is that storage and those files still treated as if they are where they were before, except the phone now thinks they are on external. Still a bit confused by the storage swap and the finer points of how it works, because now, if I'm right, if I install a new app that has secondary files, they will end up on the huge new internal storage now. But that is what these old files now on external originally were. So don't they need to end up on the new internal as well?
 
Epixtruth said:
So its ok that it didnt create any mount scripts at this point? when I go into link2sd, storage info it shows my /storage/extSdCard as the fat32 partiton correctly but it isnt mounting the 2nd partition
Click to expand...

If your on stock rom, your phone won't recognize a 2nd partition. You'll have to flash over to Victorious to get it working.
 
Epixtruth said:
So its ok that it didnt create any mount scripts at this point? when I go into link2sd, storage info it shows my /storage/extSdCard as the fat32 partiton correctly but it isnt mounting the 2nd partition
Click to expand...
Victorious hacks the mount scripts.

Did you re-flash Victorious?
 
crshortt said:
I have reinstalled Victorious. Too soon to tell how it is going, but no issues have jumped out at me yet. I finally found my original internal sdcard0 in ES File Explorer (it was not at all obvious), after first finding it using the Root Browser in ROM Toolbox, where it was very obvious. What do I need to do to deal with those files? Should they be copied to the "new" internal sd now, since that is where they originally were? Or do they need to stay there, be deleted unless they contain personal files? Not sure what their status is. Is that storage and those files still treated as if they are where they were before, except the phone now thinks they are on external. Still a bit confused by the storage swap and the finer points of how it works, because now, if I'm right, if I install a new app that has secondary files, they will end up on the huge new internal storage now. But that is what these old files now on external originally were. So don't they need to end up on the new internal as well?
Click to expand...

You can copy them if you like, the pictures and other media especially. Everything else you can just leave alone. You can still access them without copying them via gallery/music-player/video-player/etc, just have to choose the external sdcard in settings. Most apps will scan both sdcards, but you may need to tell them to re-scan or choose where to scan, if so choose both cards ro scanning (and data/media if it's an option).

The difference is now when you open apps that store media, you need to open their settings and choose to use internal or phone, instead of external or extsdcard. Your actual sdcard is now considered your internal storage.;)
 
OK, I'm very sorry to keep beating a dead horse, and being dense here, but...
I do understand that my actual 32 GB sd card is now internal sdcard0 as far as the phone is concerned. That is AWESOME btw! Thank you for this!

I also understand (I think I do anyway) that the phone now thinks its original 1.73 internal sdcard0 is now extSdCard - a place it was generally unable to store most (not all) secondary files, with the exception of whatever Link2SD was putting there in that original 2 partition. Obviously, I was able to move photo storage there, as well as certain other files like backups, music, etc. But there were certain other apps that had secondary files (for example, offline databases for Wi-Fi Finder and PeakFinder apps, and I think even Evernote, offline map caches for Google Maps, etc) that would not let me move their secondary files to external - which is where they are now? (these original files) So are the apps now able to use this "new" external card, or are they tricked into having to use the "new" internal card and the "new" extSdCard is now inaccessible to them even though they have files there? If that is indeed the case, then it is safe to delete those files from "new" external if they get recreated on "new" internal. And if an app fails to work because it can't find its files now, I need to move them to "new" internal. Anything else is safe to get rid of eventually, once I determine it is not needed on a case by case basis? And I just end up with extra storage space there for whatever I like? Is this a fair description of what is now the case, or is it totally confusing?

I promise to stop asking so many questions as soon as I am comfortable with what I have done.
 
Well another small issue... when I boot into recovery and tap install my twrp freezes and requires I pull the battery... fix permissions? Reflash twrp?
 
Epixtruth said:
Well another small issue... when I boot into recovery and tap install my twrp freezes and requires I pull the battery... fix permissions? Reflash twrp?
Click to expand...


Well I got through that issue.. just had to fix permissions.... but I am still having a hell of a time with this second partition... I see that it is really simple but I cant seem to get it right some how...

After I flashed victorious the first time I opened link2sd and got this error

"Mount script cannot be created.

mount: Invalid argument

ext4 may not be supported on your device. Try FAT32 on the second partition"

but i went in and deleted the files in \system\etc\ and flashed victorious again...

after that I ran link2sd again and it prompted as to what type of partition my second partition was... to which i just cancelled but then under storage info it said the 2nd partition was not mounted...

I know this is easy and i feel annoying to keep posting but does anyone have and idea of what i might be missing
 
Still getting this warning when I have been plugged in for a while. Never seen it until yesterday. Kind of worried about it.
2013-07-28%2012.54.21.png
 
You had to of gotten your phone really hot for it to do that. If you're doing CPU intensive tasks while charging, your phone is gonna get hot after a while. Especially if you're using mobile data
 
I was on wifi, and not doing much of anything intensive that I know of. I did switch over to the powersave governor, and it is too soon to tell yet, but it seems to be feeling no warmer than usual now, and no warnings yet. Time will tell if that actually helped I guess.
 
You must log in or register to reply here.
Back
Top Bottom