Unlocked bootload and CM10

[stcarlso]

I went through and did another pass on the issues, and managed to knock out the backlight and search key in one blow. The charger and DPI issues have also been fixed. Other than the still untested GPS, the only major issue left is the cameras - after that the kernel will be mostly completed, and we can build a ROM around it.

Does anyone know of an Android camera guru that could take a look at this one? The kernel is enumerating the cameras in the logcat

[HIGH]
I/QualcommCameraHardware( 213): getCameraInfo: loading libqcamera at 0x4005fae4
V/QualcommCameraHardware( 213): Storing the current target type as 6
I/QualcommCameraHardware( 213): getCameraInfo: numOfCameras = 2
I/QualcommCameraHardware( 213): Camera sensor 0 info:
I/QualcommCameraHardware( 213): camera_id: 0
I/QualcommCameraHardware( 213): modes_supported: 9
I/QualcommCameraHardware( 213): position: 0
I/QualcommCameraHardware( 213): sensor_mount_angle: 90
I/QualcommCameraHardware( 213): Camera sensor 1 info:
I/QualcommCameraHardware( 213): camera_id: 1
I/QualcommCameraHardware( 213): modes_supported: 5
I/QualcommCameraHardware( 213): position: 1
I/QualcommCameraHardware( 213): sensor_mount_angle: 270
V/QualcommCameraHardware( 213): getCameraInfo: dlclose(libqcamera)
I/QualcommCameraHardware( 213): getCameraInfo: OUT
[/HIGH]

but the camera app (and torch app) crashes trying to open them:

[HIGH]
I/QualcommCameraHardware( 216): Found a matching camera info for ID 0
I/QualcommCameraHardware( 216): HAL_getCameraInfo: orientation = 90
I/QualcommCameraHardware( 216): HAL_getCameraInfo: modes supported = 9
I/CameraService( 216): Opening camera 0
E/QualcommCamera( 216): Qint android::camera_device_open(const hw_module_t*, const char*, hw_device_t**): E
I/QualcommCameraHardware( 216): openCameraHardware: call createInstance
I/QualcommCameraHardware( 216): openCameraHardware:Valid camera ID 0
I/QualcommCameraHardware( 216): HAL_openCameraHardware: HAL_currentSnapshotMode = 4 HAL_currentCameraMode = 1
I/QualcommCameraHardware( 216): createInstance: E
I/QualcommCameraHardware( 216): QualcommCameraHardware constructor E
V/QualcommCameraHardware( 216): Storing the current target type as 6
V/QualcommCameraHardware( 216): constructor EX
V/QualcommCameraHardware( 216): openCamera : E
E/mm-camera( 216): postproc termination : Failed
E/mm-camera( 216): postproc_exit pp_thread exit failure!!!
E/CAM_FD ( 216): cam_conf: CAMERA_EXIT
E/mm-camera( 216): mm_camera_exec: config thread launch failed
E/QualcommCameraHardware( 216): startCamera: mm_camera_exec failed:
I/QualcommCameraHardware( 216): createInstance: created hardware=0x11fb150
V/QualcommCameraHardware( 216): startCamera E
V/QualcommCameraHardware( 216): loading liboemcamera at 0x4001f090
E/QualcommCameraHardware( 216): openCamera() failed
E/QualcommCameraHardware( 216): createInstance: startCamera failed!
E/CameraService( 216): Could not open camera 0: -1
I/CameraService( 216): Destroying camera 0
E/CameraHolder( 2480): fail to connect Camera
E/CameraHolder( 2480): java.lang.RuntimeException: Fail to connect to camera service
E/CameraHolder( 2480): at android.hardware.Camera.native_setup(Native Method)
E/CameraHolder( 2480): at android.hardware.Camera.<init>(Camera.java:323)
E/CameraHolder( 2480): at android.hardware.Camera.open(Camera.java:283)
E/CameraHolder( 2480): at com.android.camera.CameraManager.cameraOpen(CameraManager.java:224)
E/CameraHolder( 2480): at com.android.camera.CameraHolder.open(CameraHolder.java:151)
E/CameraHolder( 2480): at com.android.camera.Util.openCamera(Util.java:316)
E/CameraHolder( 2480): at com.android.camera.Camera$CameraStartUpThread.run(Camera.java:312)
[/HIGH]

 

[saxydroid]

but the camera app (and torch app) crashes trying to open them:

hove you tried other camera/ torch apps? also, could you release what you have now?

 

[stcarlso]

Other camera and flashlight apps (tried Skype, "Tiny Flashlight + LED", and a few others) all either display an error, fail silently, or force close. For a possible workaround, is there anyone still running stock ICS that can grab some camera SO files using ADB? This should not require root:
[HIGH]
adb pull /system/lib/hw/camera.msm8660.so .
adb pull /system/lib/liboemcamera.so .
adb pull /system/lib/libcameraservice.so .
[/HIGH]
If one or more of them do not exist, that's OK. I heard from TDM that these might be camera or model specific.

I am working on a release of a modified Quattrimus JB ROM for the lucid, but need to iron out several issues with making a flashable CWM package. Within a few days depending on time availability, I can post an alpha ROM that should be somewhat usable except for the cameras.

 

[chi_squared]

Hey guys I've been following this forum for quite a while now, but I just registered for the sake of posting the camera libs you want. They're attached. (Hopefully; I'm not really sure how this forum works)

EDIT: I should clarify these come from LG's stock 4.0.4 release v7. They probably didn't change between that and v8, but I realize it wasn't clear that I'm not still on GB.

 

[stcarlso]

Hey guys I've been following this forum for quite a while now, but I just registered for the sake of posting the camera libs you want. They're attached. (Hopefully; I'm not really sure how this forum works)

EDIT: I should clarify these come from LG's stock 4.0.4 release v7. They probably didn't change between that and v8, but I realize it wasn't clear that I'm not still on GB.

Thanks to all who sent the files, but as I expected, it was a no-go. Swapping out the liboemcamera.so or camera.msm8660.so files did not fix the camera, and swapping out libcameraservice.so made the phone hang on the CM splash screen. I'll keep looking into it.

EDIT:
Does anyone have libchromatix_mt9p017_preview.so from a stock ICS rom? liboemcamera.so is yearning for it, according to the logcat from the crash, and there is probably another SO file with "mt9v113" in the name as well. If those libraries load, the camera might at least power up.

 

[stcarlso]

Thanks to all who sent the files, but as I expected, it was a no-go. Swapping out the liboemcamera.so or camera.msm8660.so files did not fix the camera, and swapping out libcameraservice.so made the phone hang on the CM splash screen. I'll keep looking into it.

EDIT:
Does anyone have libchromatix_mt9p017_preview.so from a stock ICS rom? liboemcamera.so is yearning for it, according to the logcat from the crash, and there is probably another SO file with "mt9v113" in the name as well. If those libraries load, the camera might at least power up.

Thank you very much to chi_squared and greg1001 for providing the camera lib files! The rear camera and flash are now working. The front camera still cannot be opened, but we are that much closer.

 

[schlabie]

If this is released will I be able to use this instead of updating? I cant seem to update my phone, tried hard reset, and unroot and everything else I could think of.

 

[chi_squared]

Would it help to also have the file libchromatix_imx074_preview.so? find . -name "*mt9v113*" doesn't turn up any .so files, so is it possible imx074 refers to the front camera (even though I verified the front camera uses mt9v113 in logcat output)?

 

[stcarlso]

Would it help to also have the file libchromatix_imx074_preview.so? find . -name "*mt9v113*" doesn't turn up any .so files, so is it possible imx074 refers to the front camera (even though I verified the front camera uses mt9v113 in logcat output)?

That's odd. The LG Spectrum used the IMX105 file according to its config. My lucid configuration file, as you stated, has mt9v113 as the driver for the front, not this imx074 that you found. The logcat from the hang when it tries the front camera has this:
[HIGH]
I/QualcommCameraHardware( 214): receive_camframe_error_timeout: E
E/QualcommCameraHardware( 214): Camframe timed out. Not receiving any frames from camera driver
[/HIGH]
and no references to imx074. I don't think it will make a difference since the so file doesn't ask for that library.

On a side note, I have built a flashable ROM zip that I was able to load through clockwork (with a wipe of course) that booted! After a few more odds and ends are fixed, we will have an alpha quality ROM!

 

[chi_squared]

Well, the output from my above find is:
[HIGH]./sys/devices/platform/msm_camera_mt9v113.0
./sys/bus/platform/devices/msm_camera_mt9v113.0
./sys/bus/platform/drivers/msm_camera_mt9v113
./sys/bus/platform/drivers/msm_camera_mt9v113/msm_camera_mt9v113.0
./sys/bus/i2c/drivers/mt9v113[/HIGH]

so if any of those look helpful let me know and I'll send them over. Even so, I rarely (if ever) use the front camera on my phone so I'd be happy to test the ROM.

 

[stcarlso]

Well, the output from my above find is:
[HIGH]./sys/devices/platform/msm_camera_mt9v113.0
./sys/bus/platform/devices/msm_camera_mt9v113.0
./sys/bus/platform/drivers/msm_camera_mt9v113
./sys/bus/platform/drivers/msm_camera_mt9v113/msm_camera_mt9v113.0
./sys/bus/i2c/drivers/mt9v113[/HIGH]

so if any of those look helpful let me know and I'll send them over. Even so, I rarely (if ever) use the front camera on my phone so I'd be happy to test the ROM.

Those are Linux device files that are used to control the device itself, so sending those files will do nothing for us. I have put the front camera on the back burner and am working on getting us a flashable ROM. The front camera will come later, as I think it's likely a kernel issue.

 

[stcarlso]

Well, the GPS appears to not be working. So let's try what worked for the rear camera again. Could someone rip from a stock ICS ROM the following files, if they exist:

[HIGH]
adb pull /system/lib/hw/gps.msm8660.so .
adb pull /system/lib/libgps.so .
adb pull /system/lib/libgpsone_bit_api.so .
adb pull /system/etc/gps.conf .
adb pull /system/bin/gpsone_daemon .
[/HIGH]

Thank you all for your help! A preliminary CWM flashable ROM zip, for those dying to have it, should be ready for initial testing in a day or two. It may be a few weeks still before we get a stable, release quality ROM.

 

[Silverkx2000]

Well, the GPS appears to not be working. So let's try what worked for the rear camera again. Could someone rip from a stock ICS ROM the following files, if they exist:

[HIGH]
adb pull /system/lib/hw/gps.msm8660.so .
adb pull /system/lib/libgps.so .
adb pull /system/lib/libgpsone_bit_api.so .
adb pull /system/etc/gps.conf .
adb pull /system/bin/gpsone_daemon .
[/HIGH]Thank you all for your help! A preliminary CWM flashable ROM zip, for those dying to have it, should be ready for initial testing in a day or two. It may be a few weeks still before we get a stable, release quality ROM.

Hey Carl! I'm Silver! I'm from the LG Connect forums.

Just out of curiosity, we have a few kernels for our Connects...given that our phone is almost identical in specs to your phone, would you like to see if our kernels could possibly provide some assistance with the Camera and such?

 

[Connorh333]

https://www.dropbox.com/s/934rcjhmgdydglt/gps_lucid.zip?m
No such thing as "gps.msm8660.so" though.

 

[stcarlso]

Hey Carl! I'm Silver! I'm from the LG Connect forums.

Just out of curiosity, we have a few kernels for our Connects...given that our phone is almost identical in specs to your phone, would you like to see if our kernels could possibly provide some assistance with the Camera and such?

Does your phone have the same front camera chip as ours? As chi_squared clarified, we need to look at the MT9V113 driver and/or config. If it does share the camera, I'd like to take a look at any recent kernels that may be running on your phone. We would need a 3.0.x kernel with working drivers to possibly help the camera along.

Any ideas on why maps (or any other GPS app on the market) can't see a satellite or get a lock? Nothing in the logcat has anything in the way of errors, and the messages from gpsone_daemon bring up hits in the spectrum forum about CM10.1 and GPS not playing nice.

 

[stcarlso]

Well, the GPS appears to not be working. So let's try what worked for the rear camera again. Could someone rip from a stock ICS ROM the following files, if they exist:

[HIGH]
adb pull /system/lib/hw/gps.msm8660.so .
adb pull /system/lib/libgps.so .
adb pull /system/lib/libgpsone_bit_api.so .
adb pull /system/etc/gps.conf .
adb pull /system/bin/gpsone_daemon .
[/HIGH]

Thank you all for your help! A preliminary CWM flashable ROM zip, for those dying to have it, should be ready for initial testing in a day or two. It may be a few weeks still before we get a stable, release quality ROM.

Is there anyone out there still running Gingerbread (yes, the rom it comes with!) on their Lucid that can pull the GPS files mentioned in this post? TDM's fix on the spectrum worked in the same way.

EDIT:
A clean wipe AND a "reset GPS state" seemed to make the GPS start seeing satellites again with the ICS gps binaries.

Test ROM could be up by tomorrow barring any other issues. I'll put it out without a working front camera or wireless charging cover if people are willing to live without them.

 

[stcarlso]

I have compiled a test kernel + ROM for the Lucid. This early build is meant for advanced users; anyone unfamiliar with the flashing/debugging process and its inherent risks probably should wait a week or two for more testing. This ROM is almost completely the work of the Quattrimus team, with patches to the kernel and ROM as required to make it work on the lucid.

This image will only work with the gingerbread bootloader and CWM, so if you are on ICS and are dying to test it, downgrade to 2.3.6 and install CWM using the instructions posted by wiisixtyfour. You should make a full backup of whatever you have through CWM in case I messed up the ROM package and it does not boot.

EDIT: I have heard of some people being directed to this ROM from the connect/viper forums. I have not tested it on these phones and make no guarantees of it working at all. Any bricks caused by loading this test ROM, especially on another phone, shall not be mine nor any other developer's responsibility.

Link to flashable ZIP (if an error comes up, it's likely because Dropbox doesn't like everyone downloading it). You must do a clean wipe using CWM "wipe data/factory reset" before installing this version.

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

The matching google apps package (also flashable through CWM) is the same as Quattrimus. This is an Android 4.2.1 (Jelly Bean) build with a version 3.0.8 CM10.1 kernel.

What will not work:

• Front camera
• Wireless charging cover
• Car dock or media dock (phone will still charge on the dock, but the LG "Car Home"/"Desk Home" app is not included in CM and the stock one FCed if ripped)
• EDIT: There is a known issue when turning the phone on from a cold start with the AC charger plugged in, where the phone enters the "charger mode" with the screen off and will not boot normally without a battery pull. This issue is not specific to the lucid and afflicts more than a few ROMs. The workaround is to leave the phone on when charging. The issue does not occur when rebooting from the Android power menu with the charger plugged in.

What should work:

• Boot and screen, touch locations should be correct, icons/text should have usable sizes
• 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)
• Google apps
• Rear camera and flash
• AC/USB charger, battery % indicator, USB mass storage/ADB
• SD card, internal storage (mounted on /storage/sdcard1 or /storage/internal, not sure which one)

What needs to be tested:

• VPN
• MHL/Micro USB to HDMI
• Bluetooth headsets/keyboards
• WiFi Direct
• Tethering app
• General stability (run your favorite benchmark/stress test a few times, or play action games for an hour or so)
• Battery drain comparison to the stock ROM under equivalent usage

If you get a force close of something important, a logcat and dmesg would be helpful. For crashes/reboots/bootloops, use adb during the boot animation and pull "/proc/last_kmsg".

If the phone randomly hangs in a variety of places or regularly enters the "sleep of death", let me know and I'll post a standalone kernel with the clocks reduced back to the stock frequencies/voltages. This kernel runs the spectrum frequency set.

For advanced hackers, the patched kernel source is available; currently it is a few commits ahead of the kernel in the ROM linked above and may or may not be bootable at any given time.

 

[Connorh333]

I am flashing now. I will share results.
Too be honest, I'm actually really excited haha

 

[zinkscott]

I am flashing now. I will share results.
Too be honest, I'm actually really excited haha

Hey man, did everything go well for you? I've bricked my Lucid 3 times and don't want to do it again...but I would like to try this out and report back!

 

[Connorh333]

To be honest,
Everything works great. Everything is smooth and it is overclocked. Also, I have tried many things like themechooser and they all work.
The only bad thing though is that in an Antutu Benchmark the external sd read/write speed was like a 68. The overall Benchmark was in the 5000s. On ICS i had like an 8000.
Overall this rom, even though it is a "first realease," is great.
Also for stcarlso
I got Gps to work for weather
Bluetooth works fine
and it is overall stable and buttery smooth.
Battery life is a little better so far.

 

[saxydroid]

works well, everything that should work, does work. But one problem that is unrelated to the rom itself is that clockworkmod uses our internal SD card. and you cant use the usb mass storage in CWM to transfer something. the sdcard is mounted and visible via a root file explorer at /storage/sdcard1. so if you want to flash something after flashing CM 10, you will need to transfer it from your sd card to /storage/sdcard1

 

[zinkscott]

Just flashed it, all booted well. I'm currently putting all my data back on via MyBackup Pro. Will report back once I've tested it some more Thanks all

EDIT: I am having only one issue. Every time I try to send an MMS, I get "Invalid Destination" Any fixes? Seems like a Verizon thing from what I've read.

 

[stcarlso]

works well, everything that should work, does work. But one problem that is unrelated to the rom itself is that clockworkmod uses our internal SD card. and you cant use the usb mass storage in CWM to transfer something. the sdcard is mounted and visible via a root file explorer at /storage/sdcard1. so if you want to flash something after flashing CM 10, you will need to transfer it from your sd card to /storage/sdcard1

The CWM I have (flashed from ROM Manager) uses the external SD card for backup/restore, not the internal memory; perhaps mine is out of date. And at least for my lucid, the SD card is on /storage/sdcard0 and /sdcard, and the internal memory is at /storage/sdcard1. Are you sure that they are switched on your phone? EDIT: Can't read. I see what you mean.

To be honest,
Everything works great. Everything is smooth and it is overclocked. Also, I have tried many things like themechooser and they all work.
The only bad thing though is that in an Antutu Benchmark the external sd read/write speed was like a 68. The overall Benchmark was in the 5000s. On ICS i had like an 8000.
Overall this rom, even though it is a "first realease," is great.
Also for stcarlso
I got Gps to work for weather
Bluetooth works fine
and it is overall stable and buttery smooth.
Battery life is a little better so far.

Interesting. I couldn't seem to reproduce your results - my Antutu was 8349 (and this is the first time I have ever run it, so I have no comparison to ICS/GB). For the external SD read/write speed - 68 means ~6.8 MB/second, which isn't half bad. I get 93 which is ~9.3 MB/second, and it varies per SD Card.

Keep in mind that Antutu used to mistakenly measure the internal memory in the "external sd card read/write speed" column on the stock ROM, which is significantly faster than many SD cards. The stock ROM mounted the internal memory on "/sdcard", which is what most benchmarks test, while this ROM puts the external memory on /sdcard and the internal memory on /storage/sdcard1 since the spectrum had no internal memory.

 

[Connorh333]

yeah, I found my problem...
I had Force GPU rendering on while doing the benchmark.
Once I disabled it my score was somewhere in the 8000s.
Thanks for the great rom!

 

[stcarlso]

Just flashed it, all booted well. I'm currently putting all my data back on via MyBackup Pro. Will report back once I've tested it some more Thanks all

EDIT: I am having only one issue. Every time I try to send an MMS, I get "Invalid Destination" Any fixes? Seems like a Verizon thing from what I've read.

I didn't seem to have this problem, and nobody else has reported it yet. Restoring data from a backup from stock to custom may have caused this issue. Could you try a "clear data" on the messaging app? Or dialing *228? If that doesn't work, could you try wiping and testing it before restoring your data?