yashsingh1/xdaforums huggingface dataset:
[Click Android Development] dom_b:
I think you two have the best chance of making a working froyo rom if you work together based on using your roms. I use fyodors 1.6 rom daily :D
[Click Android Development] dancer_69:
I believe this too.

I prefer fyodor's rom though cause with his roms I never had problems on booting. Ikxdf' s roms from the other side don't boot on my device(except abusu 2.01 and capcake 1.01)
[Click Android Development] carlosac:
you two (ikxdf,cn.fyodor) are supermans :D make a team mix up your files and your skills, make a great panfyodorcake ROM :D and we, tattoo users will be so happy :D Good Luck :)

E: omg sry :D kiljacken and HCDR.Jacob ale supermans too :D
[Click Android Development] kiljacken:
If you send me that file or gives me the path to it in the Android source code I'll gladly take a look at it...
[Click Android Development] Albenejean:
Same here...
[Click Android Development] cn.fyodor:
Hi, ikxdf

Glad to see you in this dev thread. My kernel can drive the camera correctly, but I haven't verified it yet. Feel free to send yours to me, I'll test it to check whether it works or not.

Thanks for the info. If it's a hardware exception, there must be some bugs in my customized kernel. However, to be honest, I really don't know how to debug the C++ codes.:(

Thanks. The top path is frameworks/base/opengl. This exception error was thrown by the ./java/android/opengl/GLSurfaceView.java and the eglChooseConfig function is defined in ./libagl/egl.cpp. Hope you find something useful to debug it.
[Click Android Development] capito djjkd:
My greetings,

are the best in the tattoo improving.

Thanks to all the people who try to improve the tattoo...

let´s go friends
[Click Android Development] kiljacken:
I've looked much at the files and i have fund that the error you get is caused when an app gives some info about a configuration and EGL can't find a config that matches that information...

Does this error happen in the camera app??
[Click Android Development] ivendor:
The Exception has been thrown from JAVA because num_config[0] has not been populated by eglChooseConfig. This output parameter it's populated at the last line of eglChooseConfig.

I don't know the architecture of android and egl stuff, what i can reccomend to you is to use the LOGE macro to write in console the list of attibute (attrib_list parameter) and try to see in which point the function returns (using LOGE macro opportunely).

From what i can understand, this function tries to match the list of attributes passed as parameter(attrib_list) with global array of configurations (gConfigs), which contains 8 configurations (every configuration is an array of attributes).

Java makes 2 calls to eglChooseConfig, the first is to retrieve the number of configurations that matches the attribute list, if this number is >0 create an empty array and re-call eglChooseConfig to get the array itself populated, otherwise throws the exception you have showed in your log.
[Click Android Development] kiljacken:
I think you're right...
[Click Android Development] capito djjkd:
I think it would be important for all of us, to have a rom 100 % funcional 2.1 or 2.2 without the camera, and before fix the camera...i think

If you make a team i havent doubt could be able to make it real

thanks for all
[Click Android Development] .dot:
why?

because the devs maybe could stop developing, because they are satisfied of the working camera?

i don't think so. if they could get the camera working, there isn't a long way anymore to a 100% functional 2.1/2.2 ROM.

I hope this comes true, good luck to the devs!!!!!! :)
[Click Android Development] cn.fyodor:
I commented out the setEGLConfigChooser() stmt. in Camera/src/*/ui/GLRootView.java source file to use the GLES default config for camera. Although the 'no config match...' exception didn't come up, camera didn't snapshot any images as if the sensor didn't open. Check out the attachment below.

If the setEGLConfigChooser stmt. was added, in eglChooseConfig function, both possibleMatch and num_config will be 0. I'm trying to find the low-level reason.
[Click Android Development] segway_:
The setEGLConfigChooser() in Camera/src/*/ui/GLRootView.java source file is defined:

public void

setEGLConfigChooser (int redSize,

int greenSize, int blueSize, int alphaSize, int depthSize, int stencilSize).

All we want (i think) is the correct values for the parameters. Ok at page

http://brandnewreality.com/blog/android-egl-querying-your-gl-driver

there is a java program to query from a donut tattoo the configs....

Now we can correct the parameters at setEGLConfigChooser function.

I hope that this helps us...

seg
[Click Android Development] yash08:
Wont this method you are proposing hard coding the values?Shouldnt these be set by the user?There must be another class with the default values and which saves the user defined values.
[Click Android Development] segway_:
Look at the code:

http://android.git.kernel.org/?p=pl...0f823229da7569a51367f20c0c9d048d1cba;hb=froyo

Is it hard coded?

seg
[Click Android Development] yash08:
Well the values are hard coded.. but at the look of it I guess the hardware need these hard coded values to initialise. Good point seg.
[Click Android Development] havok123:
agreed (y)
[Click Android Development] obasio:
hey ;)

i want create this week ( I HOPE FRIDAY)a step by step how i managed to get the first frame ( <- not a shot :o ) of the preview, and i upload all files, want figure out who is the problem..

basicly i used the dedeoxed camera.apk from a 1.6 rom, and some libs.

replaced the camera.apk, ereased the dalvik cache and put the (modded) libs to /data/data/com.android.camera/libs folder, and i take some boot files from the 1.6 rom and replaced them on the fly with the 2.2 libs (adb push) and after a reboot it stucks in a bootloop ;) but i get my pretty 1 frame with the cam and it crashes after the FC dialogue, and thats all.. freeze.

the only way to reboot is a hard reset :eek:

but it works for a second :D
[Click Android Development] speedyracer5:
Much love for you and your amazing methods :P

Can you maybe release some of the files you used in doing so so some other devs can take a look at it?

Im really glad about this, the FM problem may be solved soon too so we will soon have complete roms!!!! :D:D:D:D
[Click Android Development] nick85180:
great jobs guys ;)
[Click Android Development] kaikos:
Great job! Go on with it!
[Click Android Development] apa1102:
Moto Flipout

Motorola has a phone called Flipout. This phone has a 3MP camera without AF&Flash light. Android 2.1 and QVGA.

I'm not a developer. And I can't find any ROMs of Flipout..

Seems this information still helpless :(
[Click Android Development] dront78:
Who need android 2.1 while 2.3 is coming ;) The best way IMHO do not buy HTC phones because of support quality. I'm really want xda maked android phone if it's can be realised for a sometime.
[Click Android Development] dawn2k:
As mentioned before, the flipout has a TI processesor. Tattoo is using a Qualcomm and a Qualcomm camera as well, so its very unlikely we can port the driver. (correct me if I'm wrong)

XDA is just a brand of HTC for resalers. ;)
[Click Android Development] NForce25:
I think he had in mind a phone made by developers of this forum :)
[Click Android Development] hrk:
W(hy)TF are you polluting this thread with such nonsense? You should keep this thread clean and direct such posts here. Thank you.
[Click Android Development] obasio:
moin moin :)

has some bad news, can´t solve the bootloop problem, and the reason for the freeze after the 1st frame are the modded libs.

a possible solution is to create a bash script with root premissions that replaces the needed files to run the cam "on the fly"

maybe with a startscript like:

rename "libcamera.so" -> libcamera.so.bak

rename "libcamera16.so" -> "libcamera.so"

start camera.apk (1.6)

if camera.apk is closed:

rename libcamera.so -> libcamera16.so

rename libcamera.so.bak -> libcamera.so

and that for every single file that we need to take a shot like libcamera.so, libsurfaceflinger.so and so on..

that means:

- many many more bits and bytes on the phone storage

- some more seconds (?) to start and close the camera

- and maybe the biggest problem, if you turnoff the phone before RErenaming the libs it ends in a bootloop

any ideas?:confused:
[Click Android Development] .dot:
hello!

awesome work, so we maybe have a working camera soon!

to the problem with bootloop and modified libs:

maybe you can do something with init-scripts from linux kernel.

you can start a service at booting and before shutdown. S

o you can maybe REreplace the libs at booting, if these initscripts will be executed, before bootloop appears.

another (bad) solution is to do this before the shutdown, so the script can REreplace the libs, if the user shuts down android, while in camera mode.

thanks for your work and i hope, there will be a functional camera soon :)
[Click Android Development] havok123:
make shift option if possible beats having no camera (y)
[Click Android Development] NikiB:
Are the sources of both modules available?

If yes, are there biggere differences? Maybe a merge could be possible to get it working.
[Click Android Development] arco68:
I think in order for the camera to work, a backport of the kernel drivers are needed. For example from some HTC Magic (same camera, but with autofocus) kernel sources. I've been trying, but the problem is that board-bahamas sources needs to be changed to match the new drivers. Not an easy task for someone not skilled in kernel coding.
[Click Android Development] dront78:
Fyodor has done a lot of work in this way. See git repo from first page.
[Click Android Development] arco68:
Seems that he tried the same as I did, and then reverted to default drivers.
[Click Android Development] dawn2k:
According to the things I've read in this forum the problems with the camera are not caused by the kernel. Somebody wrote, that the problem was the communication between driver and camera-app. It seems that there is no working app layer for communication between kernel and app.
[Click Android Development] SudevG:
Well, I'm not a Kernel coder but... there could be a simple solution to avoid bootloop...

startscript like:

if libcamera21.so.bak do not exists

rename "libcamera.so" -> libcamera21.so.bak

rename "libcamera16.so" -> "libcamera.so"

camera.apk is closed:

rename libcamera.so -> libcamera16.so

rename libcamera21.so.bak -> libcamera.so

May not be optimal for the performance aspect but could be some way workable..

HTH.
[Click Android Development] Jekkaman:
For those more skilled with kernel hacking and such, why don't you check the kernel source code for Huawei U8120?

The chipset is the same msm 7225, resistive screen, and 3.1 Camera with no autofocus, also runs android 2.1, maybe we can even port the hole rom.
[Click Android Development] alexcyb:
2 weeks is that I'm working on that room but to no avail
[Click Android Development] HCDR.Jacob:
Anybody tried using libcamera from this?
[Click Android Development] mannas:
AFAIK no one has tried to use it before
[Click Android Development] ikxdf:
i have already try this libs....don't work
[Click Android Development] cn.fyodor:
Camera: support devices without accelerated GL

Hi, all devs

Have anyone tried to apply this commit for our Tattoo? https://github.com/nopy/gaosp_packages_apps_Camera/commit/0f1ea9160467a1cd6b1f48ab4ceee704fb2a631f

It should be a must-have patch for msm7x25 board, like Tattoo. I have no time to work on it anymore. :(
[Click Android Development] francians:
This is a really nice patch.. maybe could fix pb like 3d gallery...

I'm sorry that you haven't the time
[Click Android Development] LokkoHTCMANIA:
This patch is already applied in CyanogenMod
[Click Android Development] manilu001:
any news about this
[Click Android Development] manilu001:
http://androgeek.com/android-2-1-based-t-mobile-pulse-mini-introduced-at-mwc.html

can this be usefull phone got 3.15 mp camera and 2.1 rom
[Click Android Development] mannas:
I think that someone had already tried to port the drivers from that phone to ours tattoo
[Click Android Development] ikxdf:
already tried
[Click Android Development] sunitknandi:
is is over yet?

Is the reverse engineering over yet? I am looking for a 2.2 rom with camera. When is it coming?
[Click Android Development] eim21048:
maybe "no" forever......:(
[Click Android Development] Prema:
Maybe this could help us on Tattoo:

snq- got the camera ported from Desire HD/Z to regular Desire, Nexus One & HD2, which no one else was able to do in months:

http://xdaforums.com/showthread.php?t=805159&page=46

Maybe we can get some insight once he explains his workflow?!
[Click Android Development] manilu001:
what about this http://www.gsmarena.com/lg_vortex-3630.php

and this http://www.gsmarena.com/lg_optimus_m-3669.php

http://www.gsmarena.com/lg_optimus_s-3583.php

http://www.gsmarena.com/lg_optimus_t-3544.php

or this http://www.gsmarena.com/lg_gt540_optimus-3081.php
[Click Android Development] ikxdf:
all with autofocus...libs cannot be copyed and imported to tattoo
[Click Android Development] manilu001:
f..kin tattoo it's so dificult to crack, if only i would know how to fix this problem, what programs are you using for programing?
[Click Android Development] francians:
surely has been tryed, but if someone wants to check..

http://gitorious.org/eclair-camera-drivers

this is the ncommander work on D/S porting

what about asking his help?
[Click Android Development] sunitknandi:
Go for it. If the G1 and Tattoo have the same camera, then porting the drivers will be very much possible.
[Click Android Development] sunitknandi:
Go for it! If the G1 and Tattoo have the same camera, driver porting will be easy.
[Click Android Development] segway_:
Yes but it is quite different at software because they have different kernel (which

developers can fix), hboot and radio (which developers cant fix cause are closed

source, something like bios on home PC). The problems on libcamera from ncommander

had disappear after radio update!

Seg
[Click Android Development] francians:
so can't we update radio from wildfire ruu?
[Click Android Development] segway_:
Can we update bios from an other motherboard?

No is the answer and this is gonna cause a brick.

Only if the two phones are hardware identical.. i think.

Seg
[Click Android Development] francians:
this "bios" should manage only radio that seems identical..

Tattoo and Wildfire have the same chipset (MSM7225) and the same radio (Qualcomm radioOne QDSP5000).

RADIO:

Tattoo: 3.35.07.20

Wildfire: 3.35.15.31
[Click Android Development] arco68:
A while ago I tried to install the Wildfire radio image on the Tattoo, but got an error, so there's probably some checks in place to prevent it.
[Click Android Development] manilu001:
new report

i try somethig today, tried instal several camera apps from market, every app FC except camera_zoom_fx_v2.4.0, it started but i got only black screen but no FC like others, maybe this help (i use SPQRom-0.6 )
[Click Android Development] lostic-b:
Try....

I view in other forum "camera magic" work on tattoo... is possible?

I no have possibility to test because have 1.6 donut...
[Click Android Development] dront78:
FC it's just a bugs in some software. The real reason of FC or black image is that no camera callback is called, so no data to process.
[Click Android Development] manilu001:
yes i understand that, but those other apps work great on 1.6
[Click Android Development] sunitknandi:
Well, u flashed with custom recovery, right? The recovery uses the bootloader to flash radio. Once u flash a HardSPL or the wildfire bootloader, the checks will be bypassed.
[Click Android Development] segway_:
Dont try this ... will brick your tattoo...

If we need an S-OFF may we can ask for help these guys:

http://alpharev.nl/

http://unrevoked.com/rootwiki/doku.php/public/forever

http://tjworld.net/wiki/Android/HTC/Vision

Seg
[Click Android Development] francians:
have tattoo support for unrevoked would be a dream! :D
[Click Android Development] sunitknandi:
Go for it. :) I am looking forward to it.

Anyway, once I flash an unrevoked spl on my phone to get s off status, can i go back to s on status with an ruu incase I feel like selling my phone?
[Click Android Development] francians:
Yes, because the S-OFF is a patched HBOOT, that you rewrite launching a RUU..
[Click Android Development] sunitknandi:
thats great then. what r we waiting for? go for it.

hopefully, this could be a nice solution for the camera and fm radio. plz do it. i would love to see newer kernels run on tattoo.
[Click Android Development] sunitknandi:
No updates yet? Has anyone done something?
[Click Android Development] francians:
Nope, sorry.. BTW afterwork I could try to contact the unrEVOked team, if none did it..
[Click Android Development] Necroduss:
Yeah since fyodor stopped developing for Tattoo I hope someone is still working on this...
[Click Android Development] Slimyth:
Thank you to all of you working hard for this. :o Hope good news soon.
[Click Android Development] PsychoRS:
Sure, some spanish people (as far as I know) are working on this.

KalimochoAz, the cooker of the Kalim Froyo CyanogenMod version for Click/Tattoo and some other testers at htcmania (spanish HTC owners forum) are making some progress on the camera.

User eliusluis recently got this:

It's a Tattoo runing Kalim's CyanogenMod 9.0 (last version) with the camera working for a while. After that, camera app closes and the image is not saved, but as you see it's going on :D

Greetz to Kalim, eliusluis and all other people from htcmania for his interest.
[Click Android Development] sunitknandi:
Thanks buddy. Just keep us updated about the news there and post the changed modules here after it is successfully ported.
[Click Android Development] magisterrivus:
GREAT news!

On that htcmania-forum someone posted a picture of his froyo-tattoo actually capturing some preview images.

With a little bit of luck we get a great christmas gift :D
[Click Android Development] speedyracer5:
Here is a logcat from htcmania of the camera capturing the first image but not saving it, can anyone help them encode JPEG from raw?
[Click Android Development] sunitknandi:
Thanks again. Just remember to post the modified apps and modules once it is proved to be working.
[Click Android Development] sunitknandi:
Wait. Let me call a guy here. arco68, francias, ivendor, u there?
[Click Android Development] XunLing:
Looking forward to cn.fyodor can solve the camera. I am also using Tattoo (>_*)
[Click Android Development] francians:
Very nice! what android version (aosp/CM/HTC based) is capturing frames? Is possible to send to our devs something? would be cool start using camera stuff (like barcode scanning) also without take photos.

I don't think stock rom use jpeg coder, but and hw coding system.
[Click Android Development] speedyracer5:
Here is a picture of the first frame off htcmania http://box.jisko.net/i/6f4f5f.jpg

and here is a translated link to the thread it is on Cyanogenmod 9.0 i believe

http://translate.google.co.uk/trans...=yaN&rls=org.mozilla:en-GB:official&prmd=ivfd
[Click Android Development] Angelde93:
No, that is the logcat capturing image in 1.6, process full for compare with the logcat in 2.2.

The logcat in 2.2 is:

I/libmm-test( 58): jpeg_buffer_use_external_buffer Thumbnail pmem failed...
E/QualcommCameraHardware( 58): native_jpeg_encode: jpeg_encoder_encode failed.
E/QualcommCameraHardware( 58): jpeg encoding failed
[Click Android Development] KalimochoAz:
I need as much help as possible.

You can try the ROM if you wan't to see it. Is based on CM 6.1.1 ( last version ).

I have offered Ivendor to join all the stuff to his github, but if he doen't want I will create a new one with all so you can see inside.

At least the problem at this moment is that camera driver works, sends me the raw image, but.... jpeg is not working. I'm working in 2 fronts, dump the raw image, or using new jpeg libs.

Your help will be welcommed

KalimochoAz
[Click Android Development] josebagar:
Does that mean that apps like barcode scanner are working?
[Click Android Development] manilu001:
can someone try this i will test if needed

http://xdaforums.com/showthread.php?t=869305
[Click Android Development] KalimochoAz:
I have no tryed more than camera, no time to do more test, I'm inside kernel and libcamera2. the problem comes from libcamera2, so I imagine all camera apps makes captures, but can't process them coz they use jpeg encoding for processing
[Click Android Development] KalimochoAz:
Do you know if there is kernel and open code from this device released?
[Click Android Development] josebagar:
Thanks for your quick reply. I believe that this app doesn't actually produce a jpeg, it just decodes the raw image as taken from the camera preview, so at first glance, it should work.

I't in the Market, in case you want to try.
[Click Android Development] manilu001:
no i just copied link i think maybe help, i tried copy files to spq rom but i don't know how to sing zip
[Click Android Development] manilu001:
maybe this help

http://xdaforums.com/showthread.php?t=809694
[Click Android Development] Jekkaman:
Huawei U8150-Ideos Kernel Source

Here is it:

Kernel Source

Rom

Thread @Modaco
[Click Android Development] magisterrivus:
KalimochoAz,

you will be our messiah. Froyo with working camera on Tattoo would just be too good to be true. All you ROM-cookers are doing things HTC is either unable or unwilling to do. Keep up your fantastic work!
[Click Android Development] KalimochoAz:
I'm not doing nothing special, just using the work of Cyanogen, Fyodor, Nopy, HDRJackob, ralle.gade... and adding few thinks. HTCMania users are giving me also a lot of help on testing all, so I have to thank their patience. As more people join the work started by our colleges more possibilities we will have on having camera working on Froyo. ( Is threre any one from HTC that can send us specs? :confused: )
[Click Android Development] magisterrivus:
What exactly do you need to know?
[Click Android Development] segway_:
That is camera specs and info...

http://www.aptina.com/support/documentation.jsp?t=0&q=22&x=38&y=7#

Seg
[Click Android Development] magisterrivus:
Here is some Linux C-Code for the mt9t013 camera in case you need to know the method signatures

http://lxr.free-electrons.com/source/drivers/staging/dream/camera/mt9t013.c?a=m68k
[Click Android Development] Necroduss:
The only reason I'm not using Froyo on my Tattoo is the camera not working. I hope this will be solved soon and best of luck to all people trying :)

I also hope this will in advance solve problem for those who will try porting Gingerbread once AOSP sources are released :D
[Click Android Development] magisterrivus:
calimochoazucarado,

what is the exact problem? Are there problems calling the jpeg_encoder callback? Or don't we know the exact signature of the encode-function? Maybe we can help.
[Click Android Development] KalimochoAz:
capture is ok, but the error is:

V/camera ( 639): mShutterToRawCallbackTime = 1291996873678ms

I/libmm-test( 58): jpeg_encoder_encode: thumbnail_fd = 1090207744 snapshot_fd = 106384

I/libmm-test( 58): dimension->ui_thumbnail_width:2055

I/libmm-test( 58): dimension->ui_thumbnail_height:2055

I/libmm-test( 58): jpeg_buffer_use_external_buffer Thumbnail pmem failed...

E/QualcommCameraHardware( 58): native_jpeg_encode: jpeg_encoder_encode failed.

E/QualcommCameraHardware( 58): jpeg encoding failed

This comes from native_jpeg_encode. I ahve to see but many thinks are extrange in this. pmem I'm sure is ok is part of the kernel, and no fail for other routines. ui_thumbnail_width:2055 and ui_thumbnail_height:2055, when captured raw is:

D/QualcommCameraHardware( 58): picture size=2048x1536

D/QualcommCameraHardware( 58): native_set_dimension: length: 28.

D/QualcommCameraHardware( 58): native_set_parm: type: 1, length=28

D/QualcommCameraHardware( 58): initRaw: initializing mThumbHeap. with size 41472

D/
[Click Android Development] marxo:
Has anyone looked at the source code of QualcommCameraHardware?

It might help :)

https://review.source.android.com/#patch,sidebyside,1776,1,libcamera/QualcommCameraHardware.cpp