[Touch Pro2, Tilt 2 Android Development] ImTuxy:
--update4 feb 18 below: camera patch + WIFI dropped connection

Hi,

Sorry to post here, as new user I don't have access to the Android development board.

I have altered [ACL]'s latest kernel (2.6.27-46 git g6a073c7 from 2 feb) to support the Rhodium 100 camera. The update package and the diff are attached.

The change does essentially the same as an earlier change to Andoid SD posted by brinka123, but is implemented differently to prevent upstream rejection as happened to the patch by brinka123. The update package is the 2 feb update that [ACL] posted with the kernel replaced. Can someone can post this to the devel board? I'm looking for testers...

Thanks,

Eric.

--update1 (new user = no new post to devel board):

Thanks arrrghhh for moving my post here. Yes, the zip can be flashed from SD card from the boot menu.

[ACL], the changes apply to all MACH_TYPE_HTCRHODIUM machines (from mach-types.h), that includes all GSM Rhodium devices I believe. I don't know how to narrow that down to the 100 alone, aside from using a kernel boot parameter.

As for the intended scope for this change: most people reporting camera issues are rhod100 users, but I've seen posts from non-rhod100 users having occasional camera crashes. Because the patch targets the used frame rate it is likely that the camera hardware in most rhod100s - and some non-100's? - just can't handle the original framerate. So if there are non-rhod100 users having occasional camera crashes...

--update2

Changed patch to make it rhod100 specific using machine_variant_type. Thanks muziling. See attached zip and diff (postfixed _1). Non-rhod100 users with crashing camera's -if any- should use the original zip to test.

Please note that this patch does not include brinka123's change for low-light conditions. Didn't that one cause problems when zooming in? I can look into that change, but would like to separate it from this patch.

Next thing I want to do is look into the audio issue when using the cam - audio runs for 1 sec, then drops. I need to go into Android code for that*

I've worked hard this evening to compile OMGB with [ACL]'s device specific files (both github), but failed miserably. Looks like I'm missing the rhodium makefiles, any pointers?

I did manage to get 7.5 GB of sources on my PC, so I guess I'm at least halfway :)

*: while recording video logcat shows a happily recording cam and then suddenly:

V/Libacoustic-wince( 85): msm72xx_start_acoustic_setting

I/AudioHardwareMSM72XX_wince( 85): disabling volume method=AUDIO

V/Libacoustic-wince( 85): msm72xx_set_acoustic_table 256 0

V/Libacoustic-wince( 85): Use current device 13

-- update3

The attachment OMGB_2.6.27.46-01399-g6a073c7-rhod100camera_1.zip lacked matching kernel modules (no wifi, ...).

Corrected that by uploading attachment OMGB_2.6.27.46-01399-g6a073c7-rhod100camera_1a.zip

Note that this second update does nothing for rhod 2xx,3xx devices.

--update4

Camera:

Some people reported improved all-rhodium camera quality under low-light conditions using brinka123's changes. The change that is present in the attached patch does improve low-light image quality somewhat as it lowers the framerate, increasing the ccd integration time (1 frame + blanking). The remaining changes from brinka123 not included in the patch do not improve low-light image quality. These changes just limit the CCD integration time to one frame incl blanking, preventing hardware enforced framerate drop but delivering a darker picture with more noise. So I think the patch as-is is fine.

Wifi:

To properly debug camera audio issues I wanted a build environment using OMGB git + [ACL]'s device_htc_rhodium git. After a week of total war between me and the Android build system I have a working environment that results in a working phone. Had to create lots of Android makefiles from scratch to do that, and by accident it resulted in a phone that doesn't drop it's WIFI connection every now and then (Wifi icon turned gray 1-2 times a day, toggling wifi off/on reconnects). The difference with [ACL]'s build is not in the code, but somewhere in the makefiles + properties + different firmware files and is difficult to narrow down. If the WiFi issue I had is real and not something limited to my phone/access points I can look into this. Anyone with this problem?