[ROM][BETA] CyanogenMod 10 for the LG Lucid


Last Updated:

  1. stcarlso

    stcarlso Well-Known Member

    DISCLAIMER: This is a CUSTOM ROM! Use at YOUR OWN RISK!!! By using this ROM, you understand that that neither I nor any other developer is liable for any or all consequences of using this ROM.

    This is CyanogenMod 10 (Android 4.1 Jelly Bean) for the LG Lucid VS840, now built from source and the work of the Quattrimus team.

    You should make a full backup of whatever you have through CWM (ClockworkMod Recovery) in case the package does not boot on your phone. If you're on stock ICS or are unsure on how to flash, see the instructions in the FAQ post. If you are upgrading from an earlier version of this ROM, you must do a "wipe cache partition" in CWM; if coming from stock or another ROM, you must do a clean wipe using CWM "wipe data/factory reset". The first boot may take 10-20 minutes on the CyanogenMod logo screen.

    Credits go to Neph81, TDM, PlayfulGod, greg1001, chi_squared, Connorh333, the Quattrimus team, the CyanogenMod team, and many others that helped to get this port off the ground.

    What should work
    • Send/receive calls, send/receive MMS, 2G/3G/4G
    • WiFi, Bluetooth, GPS (GPS may need to be reset using an app like "GPS Test" followed by ~5-10 minutes with clear view of sky with maps running and screen on)
    • Both cameras and flash
    • Internal storage (mounted on /storage/sdcard1, permissions issues fixed)
    • Wireless charging cover
    Known issues
    • Recording video using front camera hangs on stock camera application only, rear camera and Skype record fine
    • WiFi Direct causes phone to crash
    • Reboots during some games due to Adreno/EGL driver issues
    Latest version:
    Old versions:
    Older versions and basebands/stock ROMs can be found here.

    Advertisement
    FlatHead, jdulmer, Calae and 21 others like this.
  2. zinkscott

    zinkscott Well-Known Member

    What's new in the A2 build?
  3. stcarlso

    stcarlso Well-Known Member

    Changelog
    • B4 (9/30/13): Update to ZV9 RILs, use with the ZV9 baseband, possible improvements in signal/battery (your experience will vary)
    • B3 (6/25/13): Hopefully stability improvements on RIL and GPS, sleep of death kernel now default (do an advanced nandroid restore from your b2 backup of just the kernel if you weren't having issues on the higher speeds and want the extra MHz/battery)
    • B2 (3/31/13): Fix ramdisk issue, finally fix permissions on internal storage, fix ZRAM in kernel, apply TDM's logspam and WiFi power use patches, fix 4G LTE toggle, increase maximum overclock frequency to 1674 MHz
    • B1 (3/23/13): Built from source, package preserves Google apps if flashing from B1 or newer, change a few entries in build.prop, minor kernel tweaks, internal storage should be better
    • A3 (3/14/13): Tentative front camera fix, disable non-functional MHL
    • A2 (3/9/13): Fixed power-off charging issue, attempt to add wireless charging cover, minor kernel changes, add two CPU governors, fix baseband showing up as "unknown", change device to the proper "VS840 4G"
    • A1 (3/6/13): Initial release, see this post for original post

    FAQ:
    • How to flash: This image will only work with the gingerbread bootloader and CWM, so if you are on the stock ICS ROM, downgrade to 2.3.6 and install CWM using the instructions posted by wiisixtyfour (stop where it requests to flash "lucid_ics_b1.zip").
    • Kernel source: The patched kernel source is available; it may or may not be bootable at any given time!
    • Application crashes: The following methods might fix the problem (you do have a backup, right?)
      • Clearing application data and cache (Drag application icon from launcher to "App Info", click "Clear data" and "Clear cache")
      • Uninstalling and reinstalling the app
      • Wiping cache partition, wiping Dalvik Cache, and using Fix Permissions in CWM
      • If all else fails, pull a logcat to help a developer investigate:
        • Install the drivers and one-click root linked in wiisixtyfour's installation post
        • Open a Terminal or Command Prompt and change to the folder where the root script is installed
        • Run [HIGH]adb shell dmesg > dmesg.txt
          adb logcat -d > logcat.txt[/HIGH]
        • Post the files and a short description of the problem in this thread. Logs help developers like us reproduce and fix your issues!
  4. stcarlso

    stcarlso Well-Known Member

    Mostly the power-off charging fix which was bugging me (since I usually power off each night, and if I need to recharge, I had to pull the battery in the morning).
  5. PlayfulGod

    PlayfulGod Well-Known Member Developer

    nice OP format ;) lol

    If you ever recall exactly what you did to get the camera working hit me up. Its still being a pita on the Connect, but now the Gallery fc's when opening the camera.

    Also, I will push to github here in a minute, if you check it I have the proprietary-files.txt, extract-files.sh, and setup-makefiles.sh that should work for you and anyone else building for the lucid.
  6. stcarlso

    stcarlso Well-Known Member

    I think your github kernel still has a commit in it that causes a gallery/camera FC (started with fbcbdb4). If all that you changed was the config, try merging in the most recent changes on the lucid kernel github and see if the camera starts. I'm assuming you have all the SO's (including the chromatix one)? A logcat/dmesg might be helpful too as I'm still wrestling with the front cam.
  7. PlayfulGod

    PlayfulGod Well-Known Member Developer

    yea, one reason I setup the extract-files so I just pull em form the lucid run while it was installed. lol I will pull your latest kernel src.

    reverted that commit, rear camera working now, Thanks! Now to get data working.
    speedo214 likes this.
  8. schlabie

    schlabie Member

    Can't wait till this gets on ICS :D
  9. PlayfulGod

    PlayfulGod Well-Known Member Developer

    umm try again, jellybean ;) screw ics :D
  10. Keynith

    Keynith Well-Known Member

    Glad to see u guys got the bootloader unlocked! I got impatient and bought a gs3 haha oops
  11. PlayfulGod

    PlayfulGod Well-Known Member Developer

    actually they didnt, using the one from GB. ;)
  12. Keynith

    Keynith Well-Known Member

    Haha you know what i mean.
  13. stcarlso

    stcarlso Well-Known Member

    While Neph81 and I talked about a bootloader unlock, we both agreed that it would be safer to stick with the GB bootloader to reduce the number of bricks caused by mistakes unlocking. There is a well-known, fairly safe process to revert to GB + its bootloader (the KDZ unbricker), and then it takes only a few steps to install CWM and load this ROM.

    After I fix the front cam and other issues with this ROM, I'll try to pull the stock radio from ZV8 and make that a flashable package to allow people to use the CM rom with the updated baseband.
    Neph81 likes this.
  14. Connorh333

    Connorh333 Well-Known Member

    Stupid question but,
    Should I flash A2 if I am running A1 fine? Is there any stability improvements or anything like that?
  15. stcarlso

    stcarlso Well-Known Member

    It's your choice; the improvements are listed in the change log. I would do it for the power off charging issue alone, since you don't need to lose your data (just a cache wipe should be fine). Any update will uninstall any apps in /system though, so if you have a bunch of those, you may want to wait for a front camera fix.
  16. Connorh333

    Connorh333 Well-Known Member

    okay thanks! I'm flashing now. Is the power off charging issue the struggle when your phone is dead and it doesnt want to charge/turn on?
  17. stcarlso

    stcarlso Well-Known Member

    The power off charging issue was a hang on a black screen caused by plugging in the AC charger with the phone turned all the way off. The phone would charge but would not boot normally without a battery pull. Turned out to be a ramdisk issue, it's all sorted out now.
  18. PlayfulGod

    PlayfulGod Well-Known Member Developer

    What were the changes for that?? in the ramdisk?

    Also, do yall have the long pause at a blank screen during boot?? between the lg screen and the bootani, where the lg bootlogo ani was on stock.
  19. stcarlso

    stcarlso Well-Known Member

    Turns out that the power-off charger event was running a copy of "/sbin/chargerlogo" in the ramdisk meant for the spectrum. Not only did it use HD RLEs (causing the black screen), it didn't play nice with the lucid HW and would not quit when the charger was pulled. A rip from an ICS ramdisk solved both problems. Wish the same would have been true for the front cams...

    I don't have the long pause at a black screen. I used to have an issue where the backlight wouldn't illuminate for a while at boot (if you tipped the screen 45 degrees in bright light, you could see the cyanogenmod boot animation running very faintly, so it would look black in normal circumstances). However, that was fixed before A1 came out. Not sure why it would come back with a vengeance on the connect.
  20. saxydroid

    saxydroid Active Member

    Very nice job. But this is not 10.1 this is plain old 10. 10.1 is 4.2.X.
  21. platinumthomas

    platinumthomas Active Member

    I'm having an issue with the GPS. Maps can find my location, but when I try to use navigation, it displays "searching for GPS..." I used both GPS Status and GPS test to delete/clear the aGPS data and download a new file. Neither are able to find a satellite (I was in the middle of a parking lot and a beautiful sunny day as well). I've already reinstalled lucid_rom_a1. Anyone else having an issue with locking GPS satellites?
  22. Connorh333

    Connorh333 Well-Known Member

    ICS V8 modems/basebands soon...
  23. stcarlso

    stcarlso Well-Known Member

    Thanks for pointing that out, fixed. That's what I get for skimming the CyanogenMod about page instead of reading thoroughly.
  24. stcarlso

    stcarlso Well-Known Member

    I had this issue for a while, but it inexplicably fixed itself. I tried a clean wipe, among a few other things. What worked on the early spectrum builds was to flash back to stock gingerbread, enable gps, get a lock, then flash to CM10. Do either of these approaches help you?
    platinumthomas likes this.
  25. Connorh333

    Connorh333 Well-Known Member

Share This Page