yashsingh1/xdaforums huggingface dataset:
[Streak 5 Android Development] smokku:
Oh. That I wouldn't think of. Thanks for the info.

BTW, Why did you go with copying Qisda's board-qsd8x50_austin.c?

With my attempt to forward-port Streak kernel changes to MSM kernel, I didn't trust their file and went with adding needed stuff to base board-qsd8x50.c (both for Austin and Toucan). And rightly so, as I found few screw ups while porting diffs. ;)
[Streak 5 Android Development] smokku:
Could this be a reason why you don't see anything on framebuffer console?

Also, there is a difference between how kernels report fb memory:

2.6:

using 6758400 bytes of SMI at 2b00000 physical for fb

3.4:

allocating 6758400 bytes at c0e43000 (20e43000 physical) for fb

and 3.4 is missing DMA memory:

Virtual kernel memory layout:

vector : 0xffff0000 - 0xffff1000 ( 4 kB)

fixmap : 0xfff00000 - 0xfffe0000 ( 896 kB)

- DMA : 0xff000000 - 0xffe00000 ( 14 MB)

[...]

but there is something fishy about the memory:

2.6:

Memory: 232MB 254MB = 486MB total

Memory: 393292k/393292k available, 104372k reserved, 0K highmem

3.4:

Memory: 232MB 167MB = 399MB total

Memory: 387944k/387944k available, 109720k reserved, 0K highmem
[Streak 5 Android Development] FeraVolt:
Hello guys.. I'm dev from neighbour x10 forum.. I'm jut passing here with a link to a common qsd8k kernel development maintained by me...since our bards are same..

here is the link..

http://xdaforums.com/showthread.php?p=49202855

Peace!
[Streak 5 Android Development] sinan33:
Thank you FeraVolt!

I hope this could help us to fasten the development.;

Regards...
[Streak 5 Android Development] perompak13:
patient for best

i think all develop has "white flag" about our DS, but i want PING!!! them to cheers them,,,,lol

1.i want ask,,,,any tutorial about port kernel???

2. can i port kernel from other device with same spec???

3. how about ROM kernel itself???

sorry for interupt this section,,,i just wanna make our DS survive from extinction LOL :D

best regard

me
[Streak 5 Android Development] gilbert32:
any link for [MENTION=2010230]hunderteins[/MENTION]'s changes?
[Streak 5 Android Development] smokku:
https://github.com/smokku/dellstreak5-kernel-3.4/tree/msm-msm-3.4-hunderteins
[Streak 5 Android Development] FeraVolt:
http://xdaforums.com/android/software-hacking/hack-overclocking-tuning-snapdragon-s1-t2883708

Much better (Y)
[Streak 5 Android Development] hunderteins:
With the phoenix-kernel from dsc/n0p, we already have a pretty optimized cpu freqtable.

As for

# echo 0 > /sys/kernel/debug/msm_fb/0/vsync_enable

I get 33.3 fps in com.qualcomm.qx.neocore instead of 32.8 fps. That's o.k. thank you.

Changing bus_freq to 192 kHz doesn't show any effect in neocore. It's a bit less

than I expected with 'much better'

hunderteins
[Streak 5 Android Development] sinan33:
Could mikegapinski help us?
[Streak 5 Android Development] _n0p_:
I've no idea.

--

Almost forgot - don't forget to

chmod 666 /dev/msm_camera/*

--

BTW, I found the guy who actually did GB port for Streak, maybe he will help us.
[Streak 5 Android Development] sinan33:
That's perfect!

If you talk with mike; maybe he will help us?
[Streak 5 Android Development] _n0p_:
I did not see any signs of mike making anything for Streak.

My hopes are on Jagan (he worked on kernel for GB, yep it's his comments all over kernel).

And maybe kibuuka will have his Streak fixed.
[Streak 5 Android Development] abauer:
@n0p , can you compile a kernel that ignores the bb for the ICS, please , these light buttons are annoying, as i am switching between DSC and testing ICS with 366 BB.
[Streak 5 Android Development] _n0p_:
I'm actually in process of backporting kibuuka's great changes to video handling, so it may be soon, except his recent net driver fixes (mobile data accounting).
[Streak 5 Android Development] sinan33:
I can't find the exact link but i guess this link includes about camera;

https://github.com/mikegapinski/libcamera/blob/master/QualcommCameraHardware.h
[Streak 5 Android Development] abauer:
http://xdaforums.com/showthread.php?p=29859911

this idea is cool too

what kind of board has our device ?
[Streak 5 Android Development] TheManii:
I've heard offhand reports that their team's 'not exactly the most skilled' (to put it politely). From what we've seen this is more true then false, esp hearing it directly from fards when he managed to get a 'nearly almost, pre-alpha-alpha' kernal booting GB way before official 40x.

I just hope that whatever advice they provide isnt counterproductive.

I dont know if there is any one specific person to blame, and I am not blaming any specific person thuswise.

Concept is similar to what I previously mentioned for the S5/S7 threads, in that we try and 'liberate' a driver from a device with our camera module.

That specific device in the link isnt the same as ours though, ours is a VGA and 5MP one.

Repost of it is below:

To reiterate: the S5 uses a omnivision OV5642 as the rear cam module and a OV7690 as the FFC module.

The ZTE skate has a working OV5642 module compiled from source for ICS, could we merge it into our rom instead of trying to use shims to load a binary driver?

I'd imagine if it did in fact work it'd be the right step forward for if/when we/someone trys to port JB/<whatever is newest>
[Streak 5 Android Development] _n0p_:
You see, I judge by end result. Jagan with friend made it. Dj_Steeve and fards did not.

Besides, they possibly have libcamera sources from GB for our device :)

--

All current implementation for camera are HAL/wrapper solutions and not an opensource drivers (even at CodeAurora place).

Drivers actually can be made by tracing io on /dev/msm_camera, but I doubt I have enough time for that.

--

Best shot so far is the work sinan33 pointed at: Overlay patch for libui, etc.
[Streak 5 Android Development] TheManii:
Well good luck with that, I've personally been around when steve and fards talked to some of his friends in the dell team and they got absolutely nowhere with that.

Dell internal did make a half-hearted promise with us back then when we spoke with them, but well everyone knows how that ended.

The question isnt if they have it, it's that even if they did are they legally allowed to share anything with us? With dell being unfriendly they might not be able to much even if they wanted to.
[Streak 5 Android Development] _n0p_:
Android license is Apache, but kernel is GPL and Dell did not release fresh sources or patches on request.

Next, libcamera is based on old libcamera2 from CodeAurora and this again Apache, which basically means they could whatever they want with the code, as Dell has no rights for it.
[Streak 5 Android Development] abauer:
@ Manii, did you tried the modules from ZTE you mention, if yes, what's the results , any logs of the event ?

@ n0p, please don't get distracted, you are our best chance of having a fully working Ics/Jellybean, don't bet on those Dell guys helping you with anything, maybe the poor guys are looking for a job now, or focused on other works from their supervisor.

@sinan , you are so fking awesome with all those infos you provided.
[Streak 5 Android Development] _n0p_:
Todays attempt to boot with freshly built kernel failed with error in surface flinger. Might have misssed something important in kibuuka's patch.
[Streak 5 Android Development] sinan33:
Could the SIGFPE error related with the qsd8k.so error that causes surface flinger?
[Streak 5 Android Development] _n0p_:
strace could tell the exact reason, but right now have no time to play with ROMs.

--

A bit of announce - gonna be on week long vacation in a day o two.

Any new ideas are welcome.
[Streak 5 Android Development] sinan33:
Have a nice vacation!Hope to see you soon!
[Streak 5 Android Development] _n0p_:
Current trouble:

Gingerbread example:

5343 [afd0b74c] writev(4, [{"\2"..., 1}, {"OMXCodec\0"..., 9}, {"OMXCodec::Create in\0"..., 20}], 3) = 30
5343 [afd0b74c] writev(4, [{"\2"..., 1}, {"OMXCodec\0"..., 9}, {"OMXCodec::Create in: call findMat"..., 47}], 3) = 57
5343 [afd0b74c] writev(4, [{"\2"..., 1}, {"OMXCodec\0"..., 9}, {"Successfully allocated software c"..., 54}], 3) = 64
1792 [afd0b50c] open("/sys/class/msm_camera/austin/sensor", O_RDWR|O_LARGEFILE) = 25
1792 [afd0b48c] write(25, "ov5642\0"..., 7) = 7
1792 [afd0b54c] close(25) = 0
5343 [afd0b74c] writev(4, [{"\2"..., 1}, {"MediaPlayerService\0"..., 19}, {"[12] notify (0x13910, 5, 0, 0)\0"..., 31}], 3 <unfinished ...>
1792 [afd0b74c] writev(4, [{"\3"..., 1}, {"QualcommCameraHardware\0"..., 23}, {"openDualCamera: X, 1\n\0"..., 22}], 3) = 46
1792 [afd0b74c] writev(4, [{"\3"..., 1}, {"QualcommCameraHardware\0"..., 23}, {"createInstance: E\0"..., 18}], 3) = 42

ICS:

97 [4004f6c8] writev(4, [{"\3"..., 1}, {"QualcommCameraHardware\0"..., 23}, {"openDualCamera: X, 0\n\0"..., 22}], 3) = 46
97 [4004f6c8] writev(4, [{"\3"..., 1}, {"QualcommCameraHardware\0"..., 23}, {"createInstance: E\0"..., 18}], 3) = 42
97 [4004fad0] stat64("/dev/oncrpc", {st_dev=makedev(0, 10), st_ino=208, st_mode=S_IFDIR|0755, st_nlink=2, st_uid=0, st_gid=0, st_blksize=4096, st_blocks=0, st_size=620, st_atime=2012/08/22-11:50:10, st_mtime=2012/08/22-11:50:10, st_ctime=2012/08/22-11:50:10}) = 0
97 [4004f594] mmap2(0x10000000, 1048576, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS|MAP_NORESERVE, -1, 0) = 0x41c04000
97 [4004f604] mprotect(0x41c04000, 4096, PROT_NONE) = 0
97 [4005062c] clone(child_stack=0x41d03f00, flags=CLONE_VM|CLONE_FS|CLONE_FILES|CLONE_SIGHAND|CLONE_THREAD|CLONE_SYSVSEM|CLONE_DETACHED) = 1060
97 [400505cc] futex(0x22ce4, FUTEX_WAIT_PRIVATE, 0, NULL <unfinished ...>
1060 [40050470] set_tls(0x41d03f00, 0x22cc0, 0x41d03ffc, 0x40, 0x41d03f00) = 0
1060 [4004f4d8] open("/sys/class/msm_camera/austin/sensor", O_RDWR|O_LARGEFILE) = -1 EACCES (Permission denied)
1060 [4004f6c8] writev(4, [{"\6"..., 1}, {"QualcommCameraHardware\0"..., 23}, {"Sensor name not existed\n\0"..., 25}], 3) = 49
1060 [400505cc] futex(0x22ce4, FUTEX_WAKE_PRIVATE, 2147483647 <unfinished ...>
97 [400505cc] <... futex resumed> ) = 0
97 [400505cc] futex(0x4008b358, FUTEX_WAIT_PRIVATE, 2, NULL <unfinished ...>

Don't get it.

/sys/class/msm_camera/austin/sensor has media:camera permissions and even chmod'ed to 666 this error still exist.

Stuck.
[Streak 5 Android Development] _n0p_:
Fixed it - mediaserver was not in system group.

--

Anyway, still SIGFPE.

641 [4004f474] write(10, "641"..., 3) = 3
641 [4004f2ac] getpriority(PRIO_PROCESS, 641) = 20
641 [4004f274] brk(0x2b000) = 0x2b000
641 [4004f6c8] writev(4, [{"\3"..., 1}, {"CameraHAL\0"..., 10}, {"camera_set_parameters\0"..., 22}], 3) = 33
641 [4004f274] brk(0x2c000) = 0x2c000
641 [4004f6c8] writev(4, [{"\3"..., 1}, {"QualcommCameraHardware\0"..., 23}, {"setParameters: E params = 0x42658"..., 37}], 3) = 61
162 [4004f458] read(36, "\0"..., 1) = 1
641 [4004f6c8] writev(4, [{"\3"..., 1}, {"QualcommCameraHardware\0"..., 23}, {"requested preview size 640 x 480\0"..., 33}], 3) = 57
641 [4004f6c8] writev(4, [{"\3"..., 1}, {"QualcommCameraHardware\0"..., 23}, {"requested picture size 2592 x 194"..., 35}], 3) = 59
641 [4004f6c8] writev(4, [{"\3"..., 1}, {"QualcommCameraHardware\0"..., 23}, {"Set zoom=0\0"..., 11}], 3) = 35
641 [4004f690] ioctl(22, MGSL_IOCTXENABLE or MTIOCGETCONFIG <unfinished ...>
633 [4004f690] <... ioctl resumed> , 0x41e52a9c) = 0
633 [4004f690] ioctl(28, 0x40046d12, 0x41e52a20) = 0
633 [4004f690] ioctl(28, MGSL_IOCRXENABLE or MTIOCSETCONFIG, 0x41e52a14) = 0
162 [4004f554] _llseek(36, 7, [7], SEEK_SET) = 0
162 [4004f458] read(36, "\0"..., 1) = 1
162 [4004f554] _llseek(36, 8, <unfinished ...>
633 [4004f178] gettid() = 633
633 [400506b0] kill(633, SIGFPE) = 0
633 [400506b0] --- SIGFPE (Floating point exception) @ 0 (0) ---
[Streak 5 Android Development] _n0p_:
Same situation here:

http://rootzwiki.com/topic/16347-dev-ics-camera-hd-video-hw-acceleration-fix/page__st__70
[Streak 5 Android Development] abauer:
http://xdaforums.com/showthread.php?t=1427030

these guys have a working ICS camera the way n0p intends to.

I tried the libs but doesnt work by default , maybe needs some kernel tweaks.

Currently known to work on the following devices:

1) Nexus One.

2) HTC Desire

3) HTC HD2
[Streak 5 Android Development] sinan33:
Sergei;

I am almost sure that the camera issue is related with qsd8k.so error that we saw before.

I googled it today and approximately one month ago when i was trying to solve the qsd8k.so error, and i have found new files of camera with egl and qsd8k.so for solving both issue.

But i can't find the files today

---------- Post added at 07:31 AM ---------- Previous post was at 07:24 AM ----------

I think those links include the SIGFPE fix:

http://xdaforums.com/showthread.php?t=1349864&page=11

http://rootzwiki.com/topic/16347-dev-ics-camera-hd-video-hw-acceleration-fix/page__st__140
[Streak 5 Android Development] _n0p_:
abauer, this wrapper gives same SIGFPE.

strace attached.
[Streak 5 Android Development] _n0p_:
OK, problem code in liboemcamera (SIGFPE generated here) :

.text:A772A058 EXPORT vfe_util_updatescaleoutput
.text:A772A058 vfe_util_updatescaleoutput ; CODE XREF: zoom_proc+64p
.text:A772A058 ; sub_A77242C8+43Ep ...
.text:A772A058 LDR R3, =0x7094
.text:A772A05A NOP
.text:A772A05C ADR R2, loc_A772A060
.text:A772A05E PUSH {R4-R6,LR}
.text:A772A060
.text:A772A060 loc_A772A060 ; DATA XREF: vfe_util_updatescaleoutput+4o
.text:A772A060 LDR R5, =(off_A77312C0 - 0xA77310F4)
.text:A772A062 ADDS R3, R3, R2
.text:A772A064 LDR R5, [R3,R5]
.text:A772A066 ADD.W R4, R5, #0xD00
.text:A772A06A ADDS R4, #0x18
.text:A772A06C MOV R2, R4
.text:A772A06E BL VFE_MainScaleCfg
.text:A772A072 MOVW R0, #0x1190
.text:A772A076 LDR R3, [R5,R0]
.text:A772A078 TST.W R3, #1
.text:A772A07C BEQ locret_A772A08A
.text:A772A07E MOV R0, R4
.text:A772A080 BL VFE_Output1_YScaleCfg
.text:A772A084 MOV R0, R4
.text:A772A086 BL VFE_Output1_CbcrScaleCfg
.text:A772A08A
.text:A772A08A locret_A772A08A ; CODE XREF: vfe_util_updatescaleoutput+24j
.text:A772A08A POP {R4-R6,PC}
.text:A772A08A ; End of function vfe_util_updatescaleoutput

This makes me think that something is wrong with overlay surface (or it's parameters passed to liboemcamera).

Any ideas?
[Streak 5 Android Development] sinan33:
The surface flingering issue at the start of the development was related with gralloc.qsd8k.so and i saw many threads about qsd8k.so related camera issue so;

I guess the SIGFPE error and the camera issue is related with gralloc.qsd8k.so and related egl libs.

I saw that other ics devs modded those files.
[Streak 5 Android Development] abauer:
Since both overlays arent identical and the outcome is same , sinan logically is right .http://review.cyanogenmod.com/#/c/10249/1/libgralloc-qsd8k/framebuffer.cpp

To hex the liboemcamera we need someone familiar with hexing dynamically linked libs, i would say almost an impossible enterprise :crying:
[Streak 5 Android Development] _n0p_:
I wish it would be that easy.

Our problem, as it seems to me:

Our libcamera uses overlay. Other lucky smartphones does not.

This can be proved by simply looking into libcamera.so and libui.so string inside.

Yep, we are this unlucky.

Next, that Desire (ace/spade) libcamera wrapper implementation pointed by sinan actually SHOULD resolve the overlay problem. And it partially did - driver loads.

SIGFPE raised in liboemcamera itself, when it tries to calculate some values from overlay.

--

BTW, I may sound strange, but do someone have unused android phone he woudn't mind sending me? Not if I cannot afford one, but I think if I buy myself new one, i'll leave Streak as is :)
[Streak 5 Android Development] sinan33:
It is not impossible,when i was searching for the solution of each issue on the internet, i saw many devices that have the same or similar issue and the dev's solve the issue.

I believe that Sergei and Kibuuka (and jagan?) can solve this issue.
[Streak 5 Android Development] abauer:
What I meant was, that instead of looking to hex the liboemcamera, would be more logical to find out the parameters on the overlay that cause the issue, and that might bring closer to a definite solution. (a fully working JellyBean ???!!)

This might take months thou.

On the other hand , look at the fate of the devices of streak-devs, Dell support RIP, hpa`s streak RIP, Greg`s (ex-kernel guy) streak RIP, kibuuka`s streak RIP, n0p`s streak (soon to be RIP from switching between DSC and ICS).

Nazar attack LOL :laugh:
[Streak 5 Android Development] _n0p_:
Yep :)

But some stuff already found in liboemcamera - 5x5 sharpness filter matrix - can be altered (hopefully) to improve camera quality in DSC, disabling this enhancement.
[Streak 5 Android Development] sinan33:
What a heartwarming speech (!)

No pain, no gain...
[Streak 5 Android Development] _n0p_:
Since i'm almost on vacation, I just wrote to Dell, asking for prebuilt lib, as Qualcomm headers, required for bulding camera lib from CodeAurora requires proprietary headers, which are unavailable
[Streak 5 Android Development] abauer:
http://xdaforums.com/showthread.php?t=1849969

please dont expect anything from Dell, maybe they dont even have a Android dev team anymore, or they have outsourced it by now considering how cold Michael Dell was in confront to Android echosystem as a whole.
[Streak 5 Android Development] Liwais:
Nop it can can help:http://xdaforums.com/showthread.php?t=1562394

https://github.com/rapmv78/android_hardware_qcom_camerahal

We look forward :p
[Streak 5 Android Development] _n0p_:
abauer, this bugged me too, but i've found the solution:

in init.rc (located in kernel ramdisk), add system and camera groups to media server.

Or wait till Saturday when i'll be able to publish kernel with fixed mediaserver groups.
[Streak 5 Android Development] Crinos512:
:good::D
[Streak 5 Android Development] abauer:
I made changes as you said but my boot.img isnt booting and bootloops, so will wait until you come back , so keep your streak safe from getting RIP.:D

EDIT; Nevemind , it did boot but the camera still not working.
[Streak 5 Android Development] msprakashmmc:
Mike replied like this..

tell them to try other QCOM enabled repo like CM/CA.It will fix most errors like camera recording etc. than cherrypic patches

I Dont know anything about it.. So n0p, or anybody try it & tell me either does it work or what should we ask mike ..?
[Streak 5 Android Development] _n0p_:
I don't find this answer really helpful, we got a case of non-"standard" liboemcamera.
[Streak 5 Android Development] nom051205:
Nop, may you tell me why we hv (in build.prop) debug.composition.type=hw, but other roms and cm9 tree from hPA use debug.composition.type=mdp. What the effect? Last time I try and it crash status bar and wallpaper colour.
[Streak 5 Android Development] _n0p_:
https://developer.qualcomm.com/sites/default/files/composition-with-snapdragon.pdf
[Streak 5 Android Development] msprakashmmc:
Then please tell me regarding what bug we want the answer to fix dude..?
[Streak 5 Android Development] _n0p_:
I have published all info in this thread.
[Streak 5 Android Development] msprakashmmc:
Mike replied ..

" edit the hal

to contain non standard callbacks from

liboemcamera. I will send you the patch

that was helpful to me."

Is it useful....?
[Streak 5 Android Development] _n0p_:
Patches are always useful :)
[Streak 5 Android Development] msprakashmmc:
Mike sent this..

It should fix overlay based proprietary

camera libs coming from gingerbread

and froyo builds.

https://github.com/CyanogenMod/andr...mmit/738b6a8dfdcd7b38c7178f8d70d3d69c33f16551
[Streak 5 Android Development] msprakashmmc:
Tried this patch..? Any positive response guys..?
[Streak 5 Android Development] _n0p_:
You see there's not exactly a bunch of developers eagerly working on ICS port :)

--

I will try to find some tiime this week to apply and test this patch.
[Streak 5 Android Development] msprakashmmc:
ok buddy..:) waiting to taste ics :)
[Streak 5 Android Development] abauer:
That patch needs to be applied to the sources of ICS , so kibuuka can do it in 10 minutes, since he compiled ICS from AOSP git, or someone else that is willing to recompile ICS from scratch. I personally dont have time or dedication to work on the ICS.
[Streak 5 Android Development] msprakashmmc:
Hey dude, come on you can do it buddy.. Please try it man.:( but what happened to kibbuka..,?
[Streak 5 Android Development] abauer:
I am not gonna try to compile ics , am already working on the jb, and applied the patch you send
[Streak 5 Android Development] msprakashmmc:
JB..!:) woowww.. This is like double promotion dude..:) Does it fix the camera issue & does the camera working.? Or do you need any more patches ,we will get from mike dude.. When shall we expecte the JB release buddy...? Hearing this news itself makes me so happy..:)

All the very best for all your hard work..BR..
[Streak 5 Android Development] TiGuy82:
Thank you very much!

As I can see you already shared one build of JB: http://xdaforums.com/showpost.php?p=31861662&postcount=5082 :good:
[Streak 5 Android Development] _n0p_:
Attached to this post:

Lenovo S2005 camera library, kindly provided by TheManii that loads out liboemcamera without problem (as extended wrapper).

Needs to be decompiled and analyzed (as it doesn't work, but this time libcameraservice itself acts funny - "no cameraid 0").

More, as pointed by TheManii Lenovo uses same rear cam and *almost* same front one.

--

Sergei
[Streak 5 Android Development] nom051205:
Nop how we can decompile this .so file?
[Streak 5 Android Development] ilm89:
maybe IDA ?
[Streak 5 Android Development] nom051205:
Yes, i read it some where, and I have download it, let see if can work.
[Streak 5 Android Development] _n0p_:
Yes, IDA will do and this particular task is finding out why

mm_camera_get_camera_info

fails.

For me camera.msm8660.so is not very hw-dependent,

but has references to

ro.board.platform (msm7625a, msm7627a, msm7627 and msm8660 as values), ro.product.qcRefDevice, ro.hw_plat (7x25A?) properties.
[Streak 5 Android Development] ilm89:
R2 register gets false "camera_id" (loc_E948), I think.
[Streak 5 Android Development] _n0p_:
I don't believe it :)

First, hunderteins, now you :)

We finally got a team of ARM reverse engineers!(?)
[Streak 5 Android Development] hunderteins:
I think so, too. But camera.msm8660.so uses a different method to talk the the

QualcommCameraHardware than our libcamera.so from 407

For example there is no reference to /sys/class/msm_camera/ or

/sys/class/leds/spotlight/brightness.

I fear this library communicates exclusively via shared mem or /dev/oncrpc

with the kernel and the hardware dependant part is done in the kernel space.
[Streak 5 Android Development] _n0p_:
So far i learned (but i may be wrong), that kernel simply bridges the camera device via i2c bus.

No real job done there.

All communications are via liboemcamera.

And CodeAurora sources are actually half-closed source, as they doesn't provide essencial headers.

But some funcs can be used for reference, at least.
[Streak 5 Android Development] hunderteins:
hm, than there is someone else, on the other side of the /dev/onrpc. Maybe some kind of camera-service?
[Streak 5 Android Development] AWD_Maniac:
This sounds awfully familiar to the way they handle sensors (accel, ecompass, etc.). I helped fards to get them working back when there was no official Gingerbread and it was a nightmare. They use a daemon in user space which does some computations/transformations and sits between the raw signals from the kernel and Android's libs.

Can you guys point me to the latest source tree? Its been a while since I compiled a kernel for the Streak.
[Streak 5 Android Development] TheManii:
ftp.dell.com/opensource/streak/4.05_and_4.07/ for the 405 kernel src.

I dont know where the source code for the "Streak2 5" (ie the opus one) is, as lenovo might not have provided the source for it at all,

though if the kernel code doesnt do anything but bridge it wouldnt give much in the way of hints anyway(?)

The source rom in question is: 02.018.03 (SWEP_GORAB1A_v02.018.03.g_00),

the equivilent nomiclature if it were released as the "Streak2 5" would be "GORAB1A161815",

though that is also background and I dont expect it to be terribly helpful.

The (source) rom itself is an official, ota rom at least. It's not a prototype rom.