yashsingh1/xdaforums huggingface dataset:
[Galaxy S Plus I9001 Android Development] oisis:
We donąt need this file:

/system/lib/hw/sensors.GT-I9001.so

because this file is there already with name

/system/lib/hw/sensors.ariesve.so

You can check file size nad md5sum.
[Galaxy S Plus I9001 Android Development] texten:
i was googling, how to open *.so files.

for me it is not working, because i have windows :D

but with linux you can look into these.

i think its interesting to read the code of the *.so files
[Galaxy S Plus I9001 Android Development] oisis:
You can use VMPlayer, instal inside Ubuntu and start playing with libs, you will have to use command strings kinsmen.so.

EDIT1:

You can use Cygwin on Window$ to do the same. Thanks for remind me about it for achims311.
[Galaxy S Plus I9001 Android Development] texten:
i didnt know about the cygwin variant.

i already have cygwin :)

will look for that, thanks.
[Galaxy S Plus I9001 Android Development] oisis:
EDIT1

Just check in which pkg is strings.exe and install it. Should be simple :).

Here is good example :).

EDIT2:

If you want to check relations with other libs this should works:

strings libcamera.so | grep ".so"

or

strings libcamera.so | grep "lib"

To search audio string in lib:

strings libcamera.so | grep "audio"

etc....
[Galaxy S Plus I9001 Android Development] texten:
works

edit: strange output for "liboemcamera.so", but very interesting.

in this file there are almost only sensor configurations

edit1: for libcamera.so we will definitly need liboemcamera.so, maybe both files from kqb#

wow, i can see where the errors in logcats come from..

yes, we will learn much more about the files with reading in it.

the errors like "native_ext_sensor***" comes from libcamera.so

or this files is not able to set the parameters. so maybe the issue is on another configuration.

_ZN7android22QualcommCameraHardware25native_ext_sensor_config2EjPv
_ZN7android22QualcommCameraHardware24native_ext_sensor_configEjjjPv
__dso_handle
LINK_default_sensor_get_snapshot_sizes
libutils.so
libui.so
libcamera_client.so
liblog.so
libcutils.so
libmmipl.so
libbinder.so
libdl.so
libs3cjpeg.so
libc.so
libstdc++.so
libm.so
libcamera.so
[COLOR="Red"]FATAL ERROR: could not dlopen liboemcamera.so: %s[/COLOR]
liboemcamera.so
Camera sensor %d info:
sensor_mount_angle: %d
video resolution (%dx%d) with rotation (%d) is not supported, setting rotatio
o NONE
native_ext_sensor_config2 failed (cmd %d) %s
native_ext_sensor_config failed: cmd %d param1 %d param2 %d, %s
Parameter Scenemode is not supported for this sensor
Parameter Auto Scene Detection is not supported for this sensor
Parameter ISO Value is not supported for this sensor
Invalid Iso value: %s
Parameter Rolloff is not supported for this sensor
Parameter AntiBanding is not supported for this sensor
WhiteBalance not supported for this sensor
Auto Exposure not supported for this sensor
Camera Effect - %s mode is not supported for this sensor
Parameter setZoom is not supported for this sensor
SkinToneEnhancement not supported for this sensor
Set Brightness not supported for this sensor
Saturation not supported for this sensor
Contrast not supported for this sensor
Sharpness not supported for this sensor
Exposure Compensation is not supported for this sensor
set fps mode is not supported for this sensor
Set fps is not supported for this sensor
crop yuv Y destination position follows source position
crop yuv Chroma destination position follows source position
release: clearing resources done.

should we collect all output from the *so files like this?
[Galaxy S Plus I9001 Android Development] oski18:
Did you try notepad+ to open this files??

Alternatively to strings you can use this:

grep audio liboemcamera.so

or

cat liboemcamera.so | grep audio
[Galaxy S Plus I9001 Android Development] texten:
notepad++ doesnt work for *.so files..

only linux or cygwin or maybe eclipse
[Galaxy S Plus I9001 Android Development] oisis:
This is not the best way. Compare outputs from this two commands and you will see what i mean :).
[Galaxy S Plus I9001 Android Development] texten:
should the libcamera.so be compatible with liboemcamera.so?

both files are necessary. so someone should try to make them compatible?!

remember, i am no coder :D

edit:

output for liboemcamera.so:

__dso_handle
jpege_set_source
jpege_source
sensor_get_info
max_camera_iso_type
sensor_af_set_default_focus
sensor_af_move_focus
sensor_ycbcr_set_wb
isp3a_load_sensor
sensor_convert_chromatix_color_correction
sensor_convert_chromatix_color_conversion
sensor_convert_asf_3x3_matrix
sensor_post_init
sensor_get_camif_x_subsample
sensor_prepare_aec_preview
sensor_led_ctrl_init
vfe_util_get_sensor_info
vfe_util_3a_update_hw_upon_sof
vfe_util_copy_sensor
setsockopt
liblog.so
libcutils.so
libmmjpeg.so
libmmipl.so
libc.so
libstdc++.so
libm.so
liboemcamera.so
camera_ext_sensor_config
af_process_focus_sensor
sensor_set_lens_shading_correction FAILED !!!
YUV sensor, AEC_INTERESTED_REGION not supported
LED flash isn't supported for this sensor!!!
!!!Sensor Lens Shading is not supported on 3MP BAYER sensor!!!
setsockopt failed
AEC-SensorGain
Misc-PreviewResolution
Misc-SnapshotResolution
Misc-CurrResolution
Misc-SensorFormat
Misc-SensorType
Misc-SensorFullWidth
Misc-SensorFullHeight
Misc-SensorQtrWidth
Misc-SensorQtrHeight

edit2:

pm from user t5s

on Linux systems like Ubuntu you can use the command line tool "ldd" to see the dependencies of shared libraries. Unfortunately this tool is not installed on android by default.​
[Galaxy S Plus I9001 Android Development] oisis:
jpege_set_source - name of class defined in source of this lib(can be wrong).

libcutils.so - related lib or lib called by liboemcamera.so

sensor_set_lens_shading_correction FAILED !!! - error mesg, so now when somebody will read logcat and will see some errors can check from which lib is that error came

AEC-SensorGain - don't know what is in this part bud call some sensors from kernel or something like that(can be wrong).

And libOEMcamera.so is because(clik on OEM :) ). So we need all libs and files with oem in names.
[Galaxy S Plus I9001 Android Development] texten:
for future we should always be careful with both files "libcamera.so" and "liboemcamera.so".

this should be our base, after a new cm9 build

maybe still always look at "media_profiles.xml", too

all other files are not so necessary. because we have to find out which files we need realy sure.

after a update, we should always start with "libcamera.so", "liboemcamera.so" and "media_profiles.xml"
[Galaxy S Plus I9001 Android Development] :
I think this is something like background noise reduction when taking video. So it´s audio related stuff. I only know AEC as "Acoustic Echo Cancellation" a technical process for acoustic echo reduction.
[Galaxy S Plus I9001 Android Development] Daniel.96:
Can someone upload the latest working camera.apk ? and the latest camera_experimental.zip ? :)
[Galaxy S Plus I9001 Android Development] androabot:
Look here.

Camtest_base.zip

And here.

Camera.apk
[Galaxy S Plus I9001 Android Development] Daniel.96:
Thanks a lot ! :)
[Galaxy S Plus I9001 Android Development] texten:
the latest camera experimental is here: camera experimental 06

(there is no need to change the camera.apk)
[Galaxy S Plus I9001 Android Development] greendoki:
hi

don't you think you should ask that guy: mikegapinski about ics camera driver?

he's making ics for samsung wave s8500 which originaly runs bada?

chech his site: http://xdaforums.com/showthread.php?t=1596567

"Monday 2nd of June:

System is moviNAND, keyboard works and front and back camera work ! "

that's just wondoring ^^ can't wait to get ics :D

thx for you guys
[Galaxy S Plus I9001 Android Development] texten:
new cm9 build 4

so we can start more tests again.

first, here is a logcat from camera after clean install.

edit: interesting: Failed to get maximum zoom value

maybe we should test with froyo libs ^^

also: Camera.Parameters

the errors are from

QualcommCameraHardware.cpp

here is also one interesting source: read max zoom
[Galaxy S Plus I9001 Android Development] texten:
ok

while we are testing

,

here is the new camera_experimental06 fix for build 4

maybe another fix will come, after some tests.

the light version is just a

quick temporary fix

for the new build.

at this moment, after installing camera experimental 06 light,

there is no need to restore backup for further updates of cm9 or camera.

so, i think it is a better and safer solution :)

camera_experimental-06_light.zip

what does it do?

it will replace the liboemcamera.so for GT-I9001 with the one of SGH-T679.

what's the result?

the same as with camera_experimental06.zip for build3!

or maybe more ? tell us!

look here for infos: Porting State

(thanks to CastagnaIT)

info: hd is still not working! but camerascreen will be visible without changes of settings.

for better usage, change the quality in camera.apk to "sd"!

note: using these files at your own risk.

these files are provided with no warranty.

it's only for development!

how can i install it?

you will need arco68's cm9 alpha

build4

and cm9 recovery

without any other camera_experimental.zip's

1. download the zip file

2. place it on your sd card

3. boot into recovery

4. make a backup

5. wipe cache

6. wipe dalvik cache

7. install the zip

8. fix permissions

9. reboot

it is highly recommended, installing the zip only for some tests.

after installation, please report!

( how to report bugs )

SPECIAL THANKS TO:

Grabber28 & oisis & arco68

it was/is a act of hard and great teamwork!

also thanks to all user who are testing and uploading logcats, good job!
[Galaxy S Plus I9001 Android Development] :
With arcos build 4 and the actual camera_experimantal06.zip and without light-version i´m able to take photos with stock camera.apk. App freezes after taking photo, but i think it´s a huge step forward.

Log follows...

Edit: Uploaded LOG, next test will be video and front cam.

Edit2: Uploaded log. Video isn´t working proper anymore. Starts to record, freezes, works on, freezes. Had to close it manually, no video stored at sd card.

At the end of the log is a playback of an old video (build 3) shown, playback direct from google galerie.

Edit3: Uploaded LOG. when switchiong to front cam, it closes the app.

[Sent mobile][GT-I9001]

[Cyanogenmod9 by Arco]
[Galaxy S Plus I9001 Android Development] Keinbockwurst:
Awesome!!

Are there any news about the huge battery drain after using the cam? is that fixed?
[Galaxy S Plus I9001 Android Development] majokaese:
I can confirm camera.apk works, but I had to start it 3 times in a row.

EDIT: I used light version.
[Galaxy S Plus I9001 Android Development] texten:
you have to change the quality in "sd" for videorecording :)
[Galaxy S Plus I9001 Android Development] androabot:
This has already happened before, but the picture is not saved. Right?
[Galaxy S Plus I9001 Android Development] :
Know this, but don´t wanted to do, cause i wanted to check, if our camera model is supported by now.

As i wrote a few pages before, when you look at the details of a picture it says, that it was taken with an EPIC 4G, which has only a 3 MP camera. So that is the wrong setting for our camera.

I´m sorry, but till now i haven´t found, which file is for this setting...:(
[Galaxy S Plus I9001 Android Development] texten:
liboemcamera.so is our devil :D

i will look for froyo and test with this liboemcamera.so for our device.

maybe someone can took the liboemcamera.co from another device with same camera.. will be nice if we have some more liboemcamera.so's
[Galaxy S Plus I9001 Android Development] Xistance:
Well, we might be able to take the lib from i9100 because they have the same camera but the 8mp version of it. Since that camera supports 5mp it might work unlike the epic 4g which doesn't support 5mp. Sorry if this has already been done.
[Galaxy S Plus I9001 Android Development] :
The phone with the exact same HARDWARE of camera (lense, MP of front and back cam) is Galaxy S. It´s still proofen by a spare part reseller. Maybe there is a difference at chip. I´ll download and try. Don´t know if i can test it today, have a big meeting (work) tonight.
[Galaxy S Plus I9001 Android Development] texten:
for samsung S i have a liboemcamera.so

edit: sorry, i have 4 roms for galaxy s, but there is no liboemcamera.so .. so we should look on another device.
[Galaxy S Plus I9001 Android Development] :
From latest CM9 nightly? Give it a try, what can happen at all? :D
[Galaxy S Plus I9001 Android Development] texten:
also not. first i will look for our froyo...

edit: for our device was no froyo released.

you/we can also look here:

Phones with MSM8255:

- CDMA XPeria Play

- LG Revolution

- HTC Desire S

- Sony xperia mini,mini pro, neo etc - camera works

- My touch 4g - camera works

- Xperia play - camera works

- Htc desire s - camera works

- Huawei honor - official ICS

- Htc one V - no front camera but official ICS

- http://xdaforums.com/showthread.php?t=1639634

Thanks to: Spider550 for links, he cannot post here yet.

edit:

liboemcamera.so from

- Htc desire s - camera works

- Xperia play - camera works

- My touch 4g - camera works

is not working for me, stuck on bootlogo
[Galaxy S Plus I9001 Android Development] androabot:
This is a rip from de code of the Galaxy W´s liboemcamera.so
[Galaxy S Plus I9001 Android Development] texten:
at this moment we are using the liboemcamera.so from SGH-T679 for the fix
[Galaxy S Plus I9001 Android Development] Ezekiel1998:
now we are using this phone liboemcamera.so?

and what problem is want to fix now?
[Galaxy S Plus I9001 Android Development] androabot:
Work the SGH-T679 liboemcamera.so?

Can you upload it?

Thanks
[Galaxy S Plus I9001 Android Development] oisis:
You can try in this way:

1. Swap files

2. Reboot recovery

3. Wipe cache/dalvik-cache

4. Fix permissions

5. Reboot

In this way maybe will work because Android have something like control sum database for libs and after wipe there is a chance for no bootloop, can be wrong but i saw something like that in logcat.

i9001 has Snapdragon S2 MSM8255T.
[Galaxy S Plus I9001 Android Development] texten:
this is the way i always do :)

thanks for the link.

it is the camera_experimental06-light.zip
[Galaxy S Plus I9001 Android Development] androabot:
Ok thanks, then is the same lib than the Galaxy W from Arco68
[Galaxy S Plus I9001 Android Development] 30adi:
Works for me with standard camera apk, build 4 and camera_experimental-06_light.zip thanks for the hard work

edit: worked ones, now does not work, only with third party apk
[Galaxy S Plus I9001 Android Development] AndrolinRoot:
Where is our friend vpupkin? ??((
[Galaxy S Plus I9001 Android Development] texten:
thanks,

but with build4 and cameraexperimental06light with stock launcher, it will also not crash?!

i will test it.
[Galaxy S Plus I9001 Android Development] texten:
thirdpart app is still working very good.i think who realy needs a dependable camera, should use a thirdpart app
[Galaxy S Plus I9001 Android Development] texten:
i have tested nova launcher with shortcut/activity, i cant see a difference

no, when you reading logcat, it seems fc's are caused by audio- and camera- driver.

----

i decided to stop camtests for build 4, because we need more changes from arco68 at this build.

everybody who is looking for latest camfix for build 4 can look here:

camera_experimental-06_light.zip
[Galaxy S Plus I9001 Android Development] :
I understand your decission, just one more thought experiment.

The last days/weeks we did all tests with camera.msm7x30.so in /system/lib/hw.

Why? Cause when we startet our experiments we had no HAL, Firmware and right audio libs.

We took so much from GB, why not this one? =>

I think what we never tried is a combination of camera.ariesve.so with our exsisting files. But this is the original, for our phone writen lib. So maybe this will be a chance.

What do you think about it?
[Galaxy S Plus I9001 Android Development] texten:
i tried all *msm7x30* files renamed to *ariesve*. strange it works as before, too.

in kqb there is no camera*.*.so in system/lib/hw
[Galaxy S Plus I9001 Android Development] :
That´s strange, have to look for it.

Where should a have this name from if such file doesn´t exist?
[Galaxy S Plus I9001 Android Development] texten:
you can try with all files from kqb, which are the searchresult for *cam*
[Galaxy S Plus I9001 Android Development] jackq:
I think in GB is gralloc.**.so files in hw folder for camera. I see in AOKP roms for ex SGS ROM this files included and cam is working.
[Galaxy S Plus I9001 Android Development] kellermanv:
When are you gonna understand that you don't need to put files from Gingerbread ? arco said it pretty much clear, without a coder to modify the HAL, we are not going anywhere.
[Galaxy S Plus I9001 Android Development] texten:
no, there are definitly missing libs and there is definitly something to modifiy.

only the halwrapper did not caused all the errors in logcat!

sorry, but in my opinion arco has missed something.

you can read my posts in cm9 thread from last night/evening
[Galaxy S Plus I9001 Android Development] EminSG:
I'm going to test our camera with i9000 libs
[Galaxy S Plus I9001 Android Development] androabot:
Hi guys.

I do not think missing files.

I've been testing with AOKP until I got the camera work.

As you all know, Oisis doing a great job, and are including a lot of more files in rom, HOWEVER the camera still works as in the Arco68 rom.

Then I think that the work now will be modified and improved used files.
[Galaxy S Plus I9001 Android Development] kellermanv:
I think he was pretty much clear. Gingerbread files are incompatible with ICS.
[Galaxy S Plus I9001 Android Development] texten:
ah thats the reason why he used gingerbread libs in latest build?

https://github.com/arco/android_vendor_samsung_ariesve/commit/2e9c4ae785af7baf701dcb00a2b488fd7b0ce8a5

please check your knowledge before posting. don't get me wrong, but do you realy think we are joking here for all the last weeks?
[Galaxy S Plus I9001 Android Development] :
It´s so bad that i have no linux to work on camera.

Don´t get me wrong, i never took a deeper look into android kernels.

I compiled/modified linux kernels for desktop pcs 5 or 6 years ago.

So i forgot millions of thing related to that stuff, but there are a few similar steps i remember.

If anyone is able to check Android manifest and the cpp files if the values for camera release are correct, maybe there is an issue why cam freezes after taking a picture. I´m quite sure that camera itself isn´t proper released after use with ANY app.

Also there might be a mistake in getting preview back after taking photo, only thing that is strange in this contex is, that some 3rd party apps do not have this issue. So there might be some kind of override in small parts of the parameters.

Last but not least, we have the wrong values for camera resolutions, and orientation of front facing cam.

What also may be worth a look are values in build.prop and media.profiles.xml.

It seems to me that some values have to be controlled.

Just for your information: http://developer.android.com/reference/android/hardware/Camera.html
[Galaxy S Plus I9001 Android Development] texten:
here are some posts of me in cm9 thread for camera:

http://xdaforums.com/showpost.php?p=27070799&postcount=789

http://xdaforums.com/showpost.php?p=27078969&postcount=796

also, just for info.

maybe someone can do something with this informations.
[Galaxy S Plus I9001 Android Development] oisis:
You don't need installed linux on your computer, i can help you to start work wih kernel. You need Windows, 20GB free space on your hard drive and around 1GB free ram memory. In few minutes you can set up whole env develop.

EDIT:

1. Download VMachine with Ubuntu 10.04 LTS

2. Download VMPlayer

3. Extract VMachine and install VMPlayer on Windows - Run VMPlayer --> Open VMachine --> Go to extracted VMachine --> Setup VMachine(CPU cores, RAM, Network - NAT etc)

4. Download Arco kernel sources

5. Download toolchain

6. Copy toolchain and kernel sources into VMachine with Ubuntu using WinSCP

7. Extract toolchain into /opt and rename to toolchain

8. Extract kernel sources into home directory example: ~/kernel

9. Add this to ~/.bashrc(check path - must be ok!):

export CCOMPILER=/opt/linux-x86/toolchain/arm-eabi-4.4.0/bin/arm-eabi-

10. Download kernel config form your phone and copy to VMachine ~/kernel, extract and rename to .config

11. Type bash

12. Use this commands:

make ARCH=arm clean -j2
make ARCH=arm oldconfig -j2
make ARCH=arm menuconfig -j2
make ARCH=arm -j2

-j2 - setup in this way -j<NUMBER_OF_CPU_CORES_PLUS_ONE> - so if you have 2 cores in vmachine use -j3

13. Go to have a beer because compilation will take few minutes :)

14. You can copy compiled kernel and modules in this way:

mkdir -p ~/kernel-built/modules
cp ~/kernel/arch/arm/boot/zImage ~/kernel-built/
find ~/kernel/ -name "*.ko" -exec cp {} ~/kernel-built/modules/ \;

15. In ~/kernel-built/ you will have:

zImage - new kernel

modules/*.ko - all built modules

16. Next you have to create boot.img

Hope it will help :).
[Galaxy S Plus I9001 Android Development] :
That might be very close. As you know my old friend, the HP DualCore Laptop has died.

My free RAM is at ~700 MB, and my free disk space is at 33 GB.

It´s an nearly 10 year old Toshiba Satellite P20-S303.

But however, post it here!

__________________________________________________________________________

Edit: I had an idea that it have to be a virtual machine again.

I allready tried with unbuntu 10.4 in Virtual Box, was laggy as hell on this laptop.

But i´ll give it a try with VMPlayer, maybe it has a better resource management,

as my CPU is 2.67 SingleCore with 1.25 GB RAM and an old GeForce Go with 64 MB memory.

That are very week hardware specs for any kind of virtual machine enforcement at all.
[Galaxy S Plus I9001 Android Development] oisis:
Dual core will be ok, i'm compiling AOKP on similar machine but more RAM and HDD and not virtual :) , RAM - 512MB will be ok but compilation takes longer(so what if you have time), 33GB free HDD space ok as well, i think you need at least 20GB max.
[Galaxy S Plus I9001 Android Development] :
Sorry, no chance with my machine. Lags that much, i'm even not able to open a command prompt. Have to look for another computer.

[Sent mobile][GT-I9001]

[Cyanogenmod9 by Arco]
[Galaxy S Plus I9001 Android Development] gezze:
if its possible you can tell me what to change and i will let it code on my pc
[Galaxy S Plus I9001 Android Development] Slacker:
An interesting development for us sgh-t679 users, we are able to record video if we use the "attach, capture video" function in the text messaging app.

This is using the current cm9 build with no other file modifications.
[Galaxy S Plus I9001 Android Development] Keinbockwurst:
a logcat of that action would be awesome
[Galaxy S Plus I9001 Android Development] androabot:
Hello again guys

I'm thinking one thing. The Galaxy Note LTE is qualcomm to 1.5,it has ics and open source by samsung

Perhaps we could searched this code and improve things on our I9001
[Galaxy S Plus I9001 Android Development] Slacker:
Not too familiar with posting logcats, here is one while i used the text message attach function choosing capture video.

The second one is another log of the same, but in this one the camera"stopped working" twice then recorded video.

I have recorded video on both front and rear cameras using LGcamera from the market

very buggy, had black screen, hit record button, sometimes it said record failed, then it would say record start, when i stopped it it would have the button on screen to view, the player would say cannot play video, when cam app was back on screen there would be display from camera and could successfully record and then play the vid.