• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root [ROM][4.0.4][BETA] CM9 for Virgin Mobile and Sprint 10/3/2013

i guess my ?was why would both cm9 kernels run fine on gingerbread but the camera only runs on the 4 13 sorry bout the noobe stuff just trying to learn ..and thanks for your help
 
chris1975bour said:
i guess my ?was why would both cm9 kernels run fine on gingerbread but the camera only runs on the 4 13 sorry bout the noobe stuff just trying to learn ..and thanks for your help
Click to expand...

That's because with that kernel I used different camera drivers.
 
chris1975bour said:
i guess my ?was why would both cm9 kernels run fine on gingerbread but the camera only runs on the 4 13 sorry bout the noobe stuff just trying to learn ..and thanks for your help
Click to expand...

Interesting...

So, you flashed a stock based gingerbread 2.3.7 ROM, then flashed an older kernel from the CM9 build and the camera worked (gingerbread and a slightly older CM9 kernel together). You then flashed a more recent kernel from the most recent CM9 build and then everything but the camera worked. Is this correct? If so, based on what giantpune and I learned building CM7, my best guess is that this mostly worked because our device and version of gingerbread was cobbled together using source, hardware and configs found in more recent android versions. We both came to the conclusion that this device is a mess from a developer's perspective.

Edit: Nevermind, see phenomx4's answer.
 
Just a curious question...
Are kernels specific to software version(OS version) ? Is it advantageous to have a kernel version upgrade if coming from one OS version to a new one?
 
DsyMnapTic said:
Just a curious question...
Are kernels specific to software version(OS version) ? Is it advantageous to have a kernel version upgrade if coming from one OS version to a new one?
Click to expand...

AFAIK kernels have CPU, is the bridge between software and hardware, and the wrong kernel can brick your phone.
 
ktb83 said:
Interesting...

So, you flashed a stock based gingerbread 2.3.7 ROM, then flashed an older kernel from the CM9 build and the camera worked (gingerbread and a slightly older CM9 kernel together). You then flashed a more recent kernel from the most recent CM9 build and then everything but the camera worked. Is this correct? If so, based on what giantpune and I learned building CM7, my best guess is that this mostly worked because our device and version of gingerbread was cobbled together using source, hardware and configs found in more recent android versions. We both came to the conclusion that this device is a mess from a developer's perspective.

Edit: Nevermind, see phenomx4's answer.
Click to expand...

I'm still wrapping my head around some of this, but wouldn't that give credit to the idea of backporting the gb camera drivers to get it working on cm9?
 
Info by zivan56 @xda...
http://forum.xda-developers.com/showthread.php?p=20158841

ICS Camera Driver Overview

"The driver seems to be very generic to most Qualcomm SoCs, so either approach should work for many other devices.

New Driver

See CameraHal_Module.cpp from the ICS source code to see what functions needs to be implemented. It needs to be placed in /system/lib/hw/camera..so and have the struct "camera_module_t HAL_MODULE_INFO_SYM" inside the code, which the HAL looks for before loading. Once it is loaded, you must implement a few dozen functions to get it to work.

Old Driver

The old drivers primary interface with Android is through libcamera. This loads liboemcamera, which sends commands to the camera kernel driver and the Snapdragon DSP. Liboemcamera is a propriatary library with no documentation apart from the source for QualcommCameraHardware.cpp (which compiles to libcamera.so). The actual Linux kernel module is just a simple I2C bridge to control the camera, and provides no real interface."

Current code/skeleton driver available: http://forum.xda-developers.com/show...7&postcount=17

Not saying its the answer but its definitely worth investigating.
 
HaTrEd360 said:
So would maybe the post above yours show that the OE has the new driver then and everything needs to be implemented?
Click to expand...

Starks post? Is to an xda thread where they were trying to get the camera working for the galaxy ace I believe. The skeleton file is supposed to help others port the camera to their own device
 
I think I mentioned it a while back. They just did this with the Motorola Triumph. I think they used some of the GB drivers with a modified CameraHal. They documented a lot of their patches in the github source. I think it maybe worth looking at. I assume its more on an api patch level rather than a low level hardware level.

Camera forceclosing was what we got on the Triumph before christmas on CM9. They've now got both back and front facing cameras working.
 
rdoac said:
I think I mentioned it a while back. They just did this with the Motorola Triumph. I think they used some of the GB drivers with a modified CameraHal. They documented a lot of their patches in the github source. I think it maybe worth looking at. I assume its more on an api patch level rather than a low level hardware level.

Camera forceclosing was what we got on the Triumph before christmas on CM9. They've now got both back and front facing cameras working.
Click to expand...

I am already doing this and it's really close. It loads all the way but before it can show preview it crashes the camera app.
 
phenomx4 said:
I am already doing this and it's really close. It loads all the way but before it can show preview it crashes the camera app.
Click to expand...

Are you putting the libs in system/lib/hw? Seems I read that was a key difference versus gb. I'm sure you are just putting it out there.
 
At this rate you may have it before I'm able to even try to help lol in which case im sure I can find something to contribute :thumbup:
 
DMedina559 said:
So once the camera is fixed would this officially be called beta?
Or would it be beta when NFC is also fixed?
Click to expand...

This dev is hard on himself when naming his builds lol, alpha builds usually boot and maybe sensors and the launcher work. Honestly its been beta quality for the last couple releases. Once the camera is fixed its an RC imo. Phenom has done a great job and its a good clean build. :thumbup:
 
I have 3 elites ready to throw something into them lol.Once camera works I'm never going back cm all the way :-)

Sent from my LG-VM696 using Tapatalk 2
 
starkraving said:
This dev is hard on himself when naming his builds lol, alpha builds usually boot and maybe sensors and the launcher work. Honestly its been beta quality for the last couple releases. Once the camera is fixed its an RC imo. Phenom has done a great job and its a good clean build. :thumbup:
Click to expand...
I second that emotion, It is way better than any alpha I've ever seen....I am a ready tester as well seeing how I'm a "serial flasher" & all...lol
 
starkraving said:
This dev is hard on himself when naming his builds lol, alpha builds usually boot and maybe sensors and the launcher work. Honestly its been beta quality for the last couple releases. Once the camera is fixed its an RC imo. Phenom has done a great job and its a good clean build. :thumbup:
Click to expand...

I have to agree. I flashed it today and will not be going back. This is solid. I don't really care about the camera and NFC since I barely use either one.

BTW, I actually often get a 3G icon to show up, of course 1x sometimes too.

Thanks phenomx4!
 
You must log in or register to reply here.
Back
Top Bottom