05-01-2012 12:17 AM
917 ... 89101112 ...
tools
  1. java007's Avatar
    After upgrading to BB ROM 1.18 (from 1.15) and framework 1.3, I no longer get the prompt that USB is connected and whether I want to turn on USB storage when I connect it to my PC. Is there a way to get that back?
    You might want to double-check your setting for USB Debugging, it is easy to forget when you leave that checked. Unchecking the debugging box should trigger the USB storage query.

    I installed yesterday and all is working well. Very happy so far - Thanks!
    05-08-2011 10:39 PM
  2. sk8dayfuknight's Avatar
    When ever I flash the xionia recovery I get the fast boot screen when booting into recovery.. n e help?

    Sent from my LG-VM670 using Tapatalk
    05-09-2011 12:14 AM
  3. obijohn's Avatar
    When ever I flash the xionia recovery I get the fast boot screen when booting into recovery.. n e help?

    Sent from my LG-VM670 using Tapatalk
    You're probably using the xionia .6 recovery. Don't, it's compiled for the Optimus S, not V. Use .4_virgin, the one I link to in the first post.
    05-09-2011 07:13 AM
  4. davidh44's Avatar
    That's got to be an issue with the drivers on your computer. I just tested with a complete wipe and fresh install, and I still get both USB notifications on the phone when I plug it into the computer (Mac and Linux, don't have a Windows box). Maybe try reinstalling the LG windows drivers?
    I didn't have the same issue with my friend's Optimus V, so I think it maybe has to do with the SD-Ext partition created for Link2SD use. Not sure if it matters, but I used CWMA .4 Virgin recovery to create the partition - it used FAT32 for the storage partition and Ext3 for the SD-Ext partition.

    5 Google apps are removed and in a separate install zip: Gmail, Maps, Street View, and YouTube. These are removed since you can download each of them from the Market, but they're offered as an install zip in case you don't have Market access for some reason.
    Was there a 5th Google app that was removed? I'm drawing a blank on what it could be.
    05-09-2011 07:36 AM
  5. davidh44's Avatar
    You might want to double-check your setting for USB Debugging, it is easy to forget when you leave that checked. Unchecking the debugging box should trigger the USB storage query.
    It didn't make a difference in my case, but you can leave USB Debugging checked and it'll still trigger the USB storage query.
    05-09-2011 07:37 AM
  6. perksa's Avatar
    Awesome ROM!!! Haven't tested 18 yet but if the TWS is fixed I love you long time Thanks for the excellent ROM and keep up the good work.
    05-09-2011 08:19 AM
  7. easyguy's Avatar
    After updating to 1.19, I'm having problem updating google map, "page file was not signed correctly" was the error message.
    05-09-2011 12:43 PM
  8. obijohn's Avatar
    After updating to 1.19, I'm having problem updating google map, "page file was not signed correctly" was the error message.
    Install the gapps update. Or, just uninstall maps then reinstall from the market.
    05-09-2011 01:01 PM
  9. easyguy's Avatar
    Install the gapps update. Or, just uninstall maps then reinstall from the market.
    I did the gapps update after I flashed the rom. Let me try the reinstall.
    05-09-2011 01:31 PM
  10. easyguy's Avatar
    Cool, uninstall google map and reinstalling it works. Thanks Obi.
    05-09-2011 01:36 PM
  11. overthinkingme's Avatar
    Thank you for your time and effort, you're making my phone fly.

    Sent from my VM670 using Tapatalk
    05-09-2011 01:40 PM
  12. AZImmortal's Avatar
    Can I update from Bumblebee ROM 1.15 to 1.19 without wiping? I know it says it's optional when updating from a previous version in the instructions, but I seem to remember that 1.18 needed a wipe?
    05-09-2011 07:31 PM
  13. Kreatur3's Avatar
    Can I update from Bumblebee ROM 1.15 to 1.19 without wiping? I know it says it's optional when updating from a previous version in the instructions, but I seem to remember that 1.18 needed a wipe?
    Just do a nandroid back up first and have at it. Worst thing that happens is waiting a few min for the back up to restore.

    I am using 1.18 fine now. Was 1.19 just fixing issues from people going to 18 or are there other fixes/benefits to go to 19?
    05-09-2011 09:13 PM
  14. ceejay83's Avatar
    love this rom, came from rodimus and it seems BB has much better battery life
    05-09-2011 09:26 PM
  15. AZImmortal's Avatar
    Just do a nandroid back up first and have at it. Worst thing that happens is waiting a few min for the back up to restore.

    I am using 1.18 fine now. Was 1.19 just fixing issues from people going to 18 or are there other fixes/benefits to go to 19?
    Thanks for reminding me about nandroid backups. I will now update with impunity.
    05-09-2011 09:51 PM
  16. obijohn's Avatar
    I am using 1.18 fine now. Was 1.19 just fixing issues from people going to 18 or are there other fixes/benefits to go to 19?
    If you flashed the framework that was posted with 18 you have all the newest features. With 19, I figured out how to include the framework changes in the ROM itself instead of having to flash the new framework separately. One of the changes that enabled this was resigning all the system apps. This makes everything work nice together, and will allow me to enable some hidden settings (like the Hotspot settings, which I've enabled with an app for now) much easier. Look for these in the next update. If you did flash the framework on top of 18, you can wait until the next update.

    The previous poster that mentioned having an issue upgrading Gmail is probably related to this resigning (still checking for sure). Basically, in order to allow someone to flash the ROM then flash the gapps while still in recovery before booting the first time after a wipe, all the apps in /system/app have to be signed with the same key. But if you're upgrading, those apps will have a different key than expected, so to upgrade the app you may have to uninstall then reinstall the app if it gives you an invalid signature error. Some setups will work, some will have the problem, depending on if you used the gapps zip or installed from the market or flashed as a non-wipe upgrade, or, or, or... I don't like problems, so since those gapps are available on the market, and the V is a US-only model where market access isn't an issue, I may just remove the gapps install altogether so this won't be a problem for anyone else. If anyone else does report the problem, I'm sure I'll edit the first post to remove those and just let those who need them to install them
    java007 likes this.
    05-09-2011 09:55 PM
  17. Superorb's Avatar
    What exactly is the process for cooking up a new titlebar in the UOT kitchen for this ROM? I searched the thread but nothing came up for UOT.

    On another note, does anyone else here use Apps Organizer with the BB ROM? I keep getting FC's and non-responsive folders. I'm also using LauncherPro that stops responding when Apps Organizer stops responding.
    05-09-2011 11:56 PM
  18. Superorb's Avatar
    What exactly is the process for cooking up a new titlebar in the UOT kitchen for this ROM? I searched the thread but nothing came up for UOT.

    On another note, does anyone else here use Apps Organizer with the BB ROM? I keep getting FC's and non-responsive folders. I'm also using LauncherPro that stops responding when Apps Organizer stops responding.
    I copied the Framework file from the phone to the SDcard, moved it to the PC and uploaded that to the UOC kitchen. When I tried to flash the UOC zip it threw an error (status 0). I tried the workaround by moving the ROM's "META-INF/com/google/android/update-binary" file into the UOC zip but it threw a different error.

    Any ideas or advice from people who have successfully done this?
    05-10-2011 12:17 AM
  19. Superorb's Avatar
    I created a black status bar with a battery percentage indicator for this rom. Just boot into recovery (wipe the cache and dalvik to be safe), flash the zip, and reboot (it might take a few minutes)

    https://dl.dropboxusercontent.com/u/...89/blackBB.zip

    If you're performing a fresh install, you can flash this in place of update_bb_framework_1.3.zip, but it won't hurt anything if you do it after.
    So, how exactly were you able to successfully use the UOC kitchen with this ROM? I keep getting "Status 0" errors.

    EDIT: Nevermind, I used ROMtools this time and that worked great
    05-10-2011 12:19 AM
  20. Takenover83's Avatar
    So, how exactly were you able to successfully use the UOC kitchen with this ROM? I keep getting "Status 0" errors.
    That is a problem with your recovery but can be worked around in Kitchen. Just use "Amend Scripting" in the file upload tab.
    05-10-2011 12:23 AM
  21. Superorb's Avatar
    That is a problem with your recovery but can be worked around in Kitchen. Just use "Amend Scripting" in the file upload tab.
    Thanks. ROMtools works like a charm so I'm just using that.
    05-10-2011 12:53 AM
  22. sd_matto's Avatar
    Thanks, I'll update them for the next release.
    In addition to the Soundback/Talkback/Kickback trio of apps to update to latest in your next release (already done in 1.19? Or, going to happen in 1.20?), you may want to update Google Search (updated in latest LG Phoenix that I have, as well as in Market).

    Great ROM with AMAZING battery life.

    Only issue I am having is connecting via BT to my Nook Color (it pairs, but fails to connect). Anxiously waiting BT DUN/PAN on this ROM.

    Thanks again.

    One more thing: Any chance you would be willing to point me in the right direction (links? tutorial? kitchen?) to get started with ROM building for an LG Phoenix (the newly released ATT version of the Optimus One, and now my primary phone)? I think I want to take your approach to ROM building (i.e., work from stock, and modded kernel, and build out incremental improvements from there, all in pursuit of great battery life). Thanks for any help/thoughts.
    05-10-2011 12:38 PM
  23. obijohn's Avatar
    In addition to the Soundback/Talkback/Kickback trio of apps to update to latest in your next release (already done in 1.19? Or, going to happen in 1.20?), you may want to update Google Search (updated in latest LG Phoenix that I have, as well as in Market).

    Great ROM with AMAZING battery life.
    The sound/talk/kickback stuff might not be upgradeable. I've looked at it a little bit, and they appear to be modded by LG (but I may be wrong). I'll see if I can replace them with newer updates from the market while retaining the LG modifications, if any. I guess we'll see how it goes.

    As for Google Search, in the next update I will probably be removing any Google apps that can be downloaded from the market. There are only a couple left (Google Search, Voice Search, and Google Talk).

    Only issue I am having is connecting via BT to my Nook Color (it pairs, but fails to connect). Anxiously waiting BT DUN/PAN on this ROM.
    BT DUN is built into the kernel. There are some hidden settings that I will enable in the next release. This will probably be one of them.

    Thanks again.

    One more thing: Any chance you would be willing to point me in the right direction (links? tutorial? kitchen?) to get started with ROM building for an LG Phoenix (the newly released ATT version of the Optimus One, and now my primary phone)? I think I want to take your approach to ROM building (i.e., work from stock, and modded kernel, and build out incremental improvements from there, all in pursuit of great battery life). Thanks for any help/thoughts.
    Start with the kernel. Don't try to build it on anything but linux, even if you have to use VirtualBox to do it. Once you get the kernel compiled, you'll need to build a boot.img with ramdisk. The best way to do this is to unpack an existing boot.img and extract the ramdisk. Read this. However, don't use the script on the page to split the img, use unpackbootimg (you may have to compile it, but it's really simple) because it will give you the base as well as command-line arguments you need to rebuild the boot.img. Once you get that part done, you can flash the boot.img, make sure it works, tweak it, fix bugs, etc. Then put it in an update zip. Here you'll get to learn about edify scripting to flash the zip, see here.

    So, once you get the kernel going, and you've got a working boot.img and kernel update zip, you can expand on the kernel update zip to include the entire ROM. Again, it's best to start with an existing system. If you've got access to a nandroid backup of a rooted stock system, you can use unyaffs2 to extract the system.img. If the apk's and /system/framework are odexed, you'll need to deodex them. See this for info on how to do it. Make sure you can put it all in an update zip and get it installed and working before you do any further system mods. If you modify framework-res.apk, you'll need to resign it as well as every app in /system/app or the phone won't boot.

    Yep, lots of learning to do. But I just saved you, like, literally days of searching.
    05-10-2011 02:01 PM
  24. sk8dayfuknight's Avatar
    Why can't I reboot into recovery using terminal emulator by typing "reboot recovery" using this rom?

    Sent from my VM670 using Tapatalk
    05-10-2011 02:50 PM
  25. obijohn's Avatar
    Why can't I reboot into recovery using terminal emulator by typing "reboot recovery" using this rom?

    Sent from my VM670 using Tapatalk
    Because executing the "reboot" command from a terminal doesn't properly shut down the system, so it's not accessible via terminal. It's an immediate shut-down. Doing it that way is like shutting down the system with a battery pull. There's a "recovery" option from the power dialog, when you long-press the power button. Doing it that way will properly shut down the system and automatically reboot into recovery.
    05-10-2011 03:04 PM
917 ... 89101112 ...
LINK TO POST COPIED TO CLIPBOARD