Unoffical CM10 - Dell Streak 7 Alpha v1.1E

[TheManii]

We dont have the drivers period, even if we did it would still take weeks to port over the 2.2 ones even if we had them.

There's a good reason few CM9 devices have working cameras short of using the official ones from their ICS updates.

 

[Nocturnal_50]

isnt there a generic camera driver included in the JB/ICS source or why cant we use one from another CM9/CM10 rom that has a working camera (given that there is a device out there that more than likely uses the same camera in another build)

 

[TheManii]

Device drivers are by definition device specific.

Unless the manufacturer intentionally made two devices driver compatable, this isnt how it normally works.

I assume that the S7 doesnt share a common camera sensor module with a device that has working ICS drivers, or DJ_steve/giveen woulda included it a long time ago.

The most likely way to do it is to take the last available driver (the stock 5xx ones) and use/make shims to it works on ICS. But it'd likely not be an optimal solution (though anything > nothing)

 

[Nocturnal_50]

I guess if we get the build stable minus working camera then we could make a flashable zip which includes the drivers for camera at a later date (great idea but still unsure if it can be done without making the rom unstable) and include in the next build of that rom

 

[giveen]

We have a working camera driver and its baked into the ICS kernel. However the Android side of things doesn't seem to be working correctly.

 

[giveen]

Original thread updated with current status information and my github repo for this project.

 

[snargledorf]

We have a working camera driver and its baked into the ICS kernel. However the Android side of things doesn't seem to be working correctly.

Could you confirm whether my kernel has this working driver?
Were there any modifications done to the camera source for ICS-B4 to get it to work?

---------- Post added at 12:16 PM ---------- Previous post was at 12:15 PM ----------

I've been trying to look through past commits to the ICS-B4 kernel source, but it is taking some time since each commit had changes to many different areas.

 

[giveen]

Logcat of Jelly Bean booting

http://pastebin.com/e6Ta3Hvs


Snargledorf, in your logcat, search for lines like this

"

D/PrintK  (    1): <6>tegra_camera: probe
 
W/PrintK  (    1): BootLog, +ov5642_init+
 
D/PrintK  (    1): <6>ov5642 sensor driver loading
 
D/PrintK  (    1): <6>ov5642: probing sensor.
 
W/PrintK  (    1): BootLog, -ov5642_init-, ret=0
 
W/PrintK  (    1): BootLog, +ov9665_init+"

That is our camera driver loading in kernel level, but then you will see this message....

"I/CameraService(   86): CameraService started (pid=86)
 
E/CameraService(   86): Could not load camera HAL module
 "

 

[giveen]

So something is going wrong with my lights.streak7.so

 

[snargledorf]

So something is going wrong with my lights.streak7.so

Did a diff on lights and this was the only difference

-                        LOGE("write_int failed to open %s\n", path);
+                       ALOGE("write_int failed to open %s\n", path);

---------- Post added at 09:24 PM ---------- Previous post was at 09:20 PM ----------

Looks like that may be the ticket

I/DEBUG   (   82):     5bd9e824 00737365 000a6425 6867696c 77007374  ess.%d..lights.w
 
I/DEBUG   (   82):     5bd9e834 65746972 746e695f 69616620 2064656c  rite_int failed
 
I/DEBUG   (   82):     5bd9e844 6f206f74 206e6570 000a7325 4449564e  to open %s..NVID
 
I/DEBUG   (   82):     5bd9e854 56204149 61746e65 6c20616e 74686769  IA Ventana light

 

[giveen]

Per our discussion, that wasn't it.

After digging around, I came across the HTC Endeavour (a Tegra 3 device) with a very nice looking lights code with it being "lights.tegra", I ripped it, changed the log values to match jelly bean, and compiling now

 

[giveen]

Anyone know how to tell it to NOT compile goldfish stuff?

 

[azrael293]

Anyone know how to tell it to NOT compile goldfish stuff?

I searched around online and found some info, hopefully helpful, in another forum - http://forum.xda-developers.com/showthread.php?t=1475358&page=185

says he basically deleted it out and just had to repush a few files that didnt work after and that fixed the issue. seems it only loads those during emulation and not during the actual device boot (if i read that correctly).

 

[giveen]

Lights solved;
New error

W/dalvikvm(  696): threadid=20: thread exiting with uncaught exception (group=0x40b38300)

I/Process (  696): Sending signal. PID: 696 SIG: 9

I/SystemServer(  696): Vibrator Service

E/AndroidRuntime(  696): *** FATAL EXCEPTION IN SYSTEM PROCESS: UEventObserver

E/AndroidRuntime(  696): java.lang.RuntimeException: Unable to open socket for UEventObserver

E/AndroidRuntime(  696): 	at android.os.UEventObserver.native_setup(Native Method)

E/AndroidRuntime(  696): 	at android.os.UEventObserver.access$000(UEventObserver.java:39)

E/AndroidRuntime(  696): 	at android.os.UEventObserver$UEventThread.run(UEventObserver.java:97)

 

[azrael293]

Lights solved;
New error

W/dalvikvm(  696): threadid=20: thread exiting with uncaught exception (group=0x40b38300)

I/Process (  696): Sending signal. PID: 696 SIG: 9

I/SystemServer(  696): Vibrator Service

E/AndroidRuntime(  696): *** FATAL EXCEPTION IN SYSTEM PROCESS: UEventObserver

E/AndroidRuntime(  696): java.lang.RuntimeException: Unable to open socket for UEventObserver

E/AndroidRuntime(  696): at android.os.UEventObserver.native_setup(Native Method)

E/AndroidRuntime(  696): at android.os.UEventObserver.access$000(UEventObserver.java:39)

E/AndroidRuntime(  696): at android.os.UEventObserver$UEventThread.run(UEventObserver.java:97)

Did some more research for ya. An android team member in a group question stated this type of error is likely due to a permissions issue (tho he didnt mention a fix).

Here is a link to some info on ueventobserver I found tho that could possibly help. http://www.androidjavadoc.com/1.1_r1_src/android/os/UEventObserver.html

Ill keep looking for more on it until we crack it.

Sent from my DROID4 using xda app-developers app

 

[ikutoisahobo]

Awesome, looks like this project is back on track!

 

[giveen]

See OP....

 

[snargledorf]

Congrats giveen

Sent from my SPH-D700 using Tapatalk 2

 

[TheManii]

Any chance of looking to get 128dpi working?

128dpi would make the S7 have (roughly) the same DP as the N7
(DPs take into account the native res x DPI).

Unfortuantely though 128dpi is completely unsupported while 213dpi (aka TVDPI) is supported.

128dpi causes CM9-mod/systemui to simply crash


I ask since JB natively supports the N7 which is:

	Res      dpi	width (in DP)		height (in DP)
N7	[email protected]	961.5023474178404	600.9389671361502
S7	800x480 @128	1000			600

(for the N7, round the values down)

Hence the N7 UI is roughly designed around 600dp(?)

 

[giveen]

I'll try to bump it a bit more and see how GUI handles it.