ARCHIVED: [DEAD ROM] nROM v1.6.3

[lionedas]

Nick

Using 1.5.1 after VC update.


Noticed that when i remove the micro sd card, I have to manually re mount it via settings,
it used to mount on its when I would re insert it via stock rom.

also seems kinda quite in the forum, no one seems to be putting out any new roms

I smell something cooking.....

 

[kenny70452]

Nick

Using 1.5.1 after VC update.


Noticed that when i remove the micro sd card, I have to manually re mount it via settings,
it used to mount on its when I would re insert it via stock rom.

also seems kinda quite in the forum, no one seems to be putting out any new roms

I smell something cooking.....

Same thing here with the card. No big deal, seldom remove the card anyway.

 

[Nick7]

That is how the new driver works

 

[phufool]

Hi and thanks for the rom, it works great on VC! I was wondering if there's anything I can do to free memory on the phone? On the ThundeROM I had a lot more free space and I'm running out of space for the nROM already. Thanks.

 

[Nick7]

Hi and thanks for the rom, it works great on VC! I was wondering if there's anything I can do to free memory on the phone? On the ThundeROM I had a lot more free space and I'm running out of space for the nROM already. Thanks.

Boot to recovery and clear you cache and dalvik cache. Should be good after that.

 

[phufool]

I wiped the cache and delvik cache using Xionia Clockwork Custom Recovery and I still have the same amount of memory, except now some of my apps/games are gone lol. Did I do something wrong?

 

[Nick7]

I wiped the cache and delvik cache using Xionia Clockwork Custom Recovery and I still have the same amount of memory, except now some of my apps/games are gone lol. Did I do something wrong?

type "busybox df" in terminal emulator or adb shell and let me know what it says.

 

[phufool]

busybox df
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 217408 12 217396 0% /dev
/dev/block/mtdblock1 127104 1196 125908 1% /cache
/dev/block/mtdblock5 162304 120456 41848 74% /system
/dev/block/mtdblock6 168832 147772 21060 88% /data
/dev/block/mtdblock8 1536 1156 380 75% /persist
tmpfs 217408 0 217408 0% /mnt/asec
/dev/block/vold/179:1
7753728 1908220 5845508 25% /mnt/sdcard
/dev/block/vold/179:1
7753728 1908220 5845508 25% /mnt/secure/asec
/dev/block/dm-0 11424 9664 1760 85% /mnt/asec/au.com.phil.ab
duction2-1
/dev/block/dm-1 18688 16836 1852 90% /mnt/asec/com.rovio.angr
ybirds-1
/dev/block/dm-2 16612 14824 1788 89% /mnt/asec/com.rovio.angr
ybirdsseasons-1
/dev/block/dm-3 2088 500 1588 24% /mnt/asec/org.jfedor.fro
zenbubble-1
/dev/block/dm-4 4164 2640 1524 63% /mnt/asec/smpxg.crystall
ight-1
/dev/block/dm-5 18688 16608 2080 89% /mnt/asec/com.alleylabs.
MeteorBlitz-1
/dev/block/dm-6 7276 6084 1192 84% /mnt/asec/com.com2us.sli
ceit-1

Sidenote: terminal emulator didn't work so I used adb shell. It said "The application Terminal Emulator (process com.android.term) has stopped unexpectedly. Please try again.

 

[Nick7]

Yeah dalvik-cache isn't bind mounting to cache. What version of nROM are you running and what steps did you take to flash?

 

[phufool]

I have v1.5.1
Hmm what steps did I take to flash the ROM? I converted back to stock -> updated to VC using LG Update Tool -> Rooted -> Installed Xionia Clockwork -> Flashed nROM using Xionia Clockwork
I didn't wipe anything before installing nROM

 

[Nick7]

I have v1.5.1
Hmm what steps did I take to flash the ROM? I converted back to stock -> updated to VC using LG Update Tool -> Rooted -> Installed Xionia Clockwork -> Flashed nROM using Xionia Clockwork
I didn't wipe anything before installing nROM

Interesting. If it isn't too much of a hassle do a full wipe and reflash but there is no reason that dalvik-cache to cache shouldn't be working. Did you flash any kernels over the ROM?

 

[phufool]

Oh I did flash the Xionia Kernel after flashing nROM. Is that the problem? :O

 

[Nick7]

Oh I did flash the Xionia Kernel after flashing nROM. Is that the problem? :O

Yep that's it, reflash nROM and you'll be good to go. nROM already includes Xionia kernel.

 

[el3men7]

Voicemail notifications gone?

I noticed with the 1.5.1 build that I'm no longer receiving voicemail notifications in the notification bar. Is anyone else seeing this, or is this related to my inability to update profile/PRL?

On a somewhat related note, I was unable to follow the recommended instructions in post #531 of updating my profile on the 1.4.5 build, since I receive the hands free activation error even on 1.4.5.

Nick: thanks for all your hard work on this awesome ROM! I'm very eagerly looking forward to trying out your Lego Rom as soon as my activation issues are resolved.

 

[Nick7]

I removed the voicemail application, but if you would like I provided it for re-installation in my download page. Check it out. And don't stress too much about the PRL or profile, you are probably up to date on those anyways.

 

[tmeader]

Nick, I'm looking to move to the VC baseband (since I can't help myself not having the "latest") and just want to know if what I'm thinking is possible. I realize I will have to go through the entire process of reverting back, flashing with the LG tool, and then getting the recovery back on there (Thunderc in my case, since for the life of me the Xionia one would not install without rebooting to the LG logo and hanging)... but after that, is it possible to just restore a nandroid backup of 1.5.1 (currently running on baseband V9) and be good to go?

As for nandroid backups, the Thunderc recovery has 4 options, so I'd like to know exactly which one I need to restore EVERYTHING correctly?

-Nand backup
-Nand backup + .android_secure
-Nand backup + ext
-Nand + ext + .android_secure

I'm guessing the latter, but just want to make sure.

Two more quick questions:

1) I noticed in the new sticky that KSmithInNY posted that nROM isn't listed as "optimized" vs the others. What exactly is that referring to? Is it possible to do so in the future builds?

2) After I flash to VC, is it fine to move to the 008 xionia kernel with nROM? I know if comes with 007, and that seems to work fine. But it's stated rather blatantly on the kernel thread that 008 should only be used on the VC baseband. Any thoughts?

Thanks in advance.

 

[Nick7]

Nick, I'm looking to move to the VC baseband (since I can't help myself not having the "latest") and just want to know if what I'm thinking is possible. I realize I will have to go through the entire process of reverting back, flashing with the LG tool, and then getting the recovery back on there (Thunderc in my case, since for the life of me the Xionia one would not install without rebooting to the LG logo and hanging)... but after that, is it possible to just restore a nandroid backup of 1.5.1 (currently running on baseband V9) and be good to go?

As for nandroid backups, the Thunderc recovery has 4 options, so I'd like to know exactly which one I need to restore EVERYTHING correctly?

-Nand backup
-Nand backup + .android_secure
-Nand backup + ext
-Nand + ext + .android_secure

I'm guessing the latter, but just want to make sure.

Two more quick questions:

1) I noticed in the new sticky that KSmithInNY posted that nROM isn't listed as "optimized" vs the others. What exactly is that referring to? Is it possible to do so in the future builds?

2) After I flash to VC, is it fine to move to the 008 xionia kernel with nROM? I know if comes with 007, and that seems to work fine. But it's stated rather blatantly on the kernel thread that 008 should only be used on the VC baseband. Any thoughts?

Thanks in advance.

Normal nand backup will work fine. The reason I didn't upgrade is because I had no luck rooting VC.

1) The only difference would be having a VC radio. I don't think there is really any other additional optimization. If you updated to VC you would have that same "optimization."

2) I would stick with 007. I think 008 was designed for Gingerbread / CM 7 but I could be wrong.

IMO there is no reason to update. It's just a PITA

 

[KSmithInNY]

Optimization = PNG optimization.

This may have changed but last we chatted nick but you had mentioned didn't do png optimization. If that's changed, let me know so i can update the list.

 

[Nick7]

Optimization = PNG optimization.

This may have changed but last we chatted nick but you had mentioned didn't do png optimization. If that's changed, let me know so i can update the list.

Ah okay, thanks for the clarification. I PNG optimized framework -res but that's it

 

[KSmithInNY]

Ah okay, thanks for the clarification. I PNG optimized framework -res but that's it

What the heck man finish off that bad boy. I will say it's a fine art on what can and can't be optimized but most of the images really enjoy it It's like lipo suction for apk's!! lmfao