Hey guys!
Many developers have fixed the bug of the camera for many devices Arm v6. I have compiled the rom for Huawei u8650 CM9 from source but the camera does not work. It has never worked even with other porting always based on 4.0.x CyanogenMod. Where is the mistake? Kernel or libraries Camera? I ask your help in order to fix the source
Thank you so much!!
Logcat will help you identifying the cause for the problem...
Btw it can both be a kernel and lib problem...
does not work
I would love this issue to be resolved.
Hi all,
I create this thread for annotate my progress in debugging @FXP's CM10 @munjeni CM11 and for create a guide to new developers. So.. Let's start
Quick start:
Get all necessay software in order to compile CyanogenMod's source code: here there is a very good guide by @elia222, I have no more to add.
Get CyanogenMod 's source code as described here but use this device tree.
Debugging using catlog, dmesg and brain.
Goals:
Some of this bugs are already fixed by other users, all credits to relative developers (if you are one of this and I have not mentioned you, or I make a mistake about credits please send me a PM).
Fix Bluetooth ✓
Fix Wi-Fi ✓
Fix Wi-Fi Tethering ✓
Fix Wi-Fi Direct ✓
Fix Camcorder ✓
Fix LED bar ✓
Fix FM radio
Fix main camera upside-down (Fixed here by @Na'onak ):
This fix consist in use right camera file as FreeXperia use the Xperia GO version. The right file can be downloaded from here.
After have substituted the file in relative CyanogenMod's build folder, recompile and flash.
Fix ambient sensor light (Fixed here + this post by @munjeni + @95A31):
This fix consist in adjust ambient sensor light driver. In detail Android Jelly Bean require als_lx parameter that is not in standatd driver source code. This parameter and relative functions were added by @munjeni in the safest possible way: return a fixed value. The fix consist in implement this new functions exploiting the already present functions. The original version can be dowloaded here and the newest is attacched at bottom of this post. After have substituted the file in relative CyanogenMod's build folder, recompile and flash.
good thread, try this, to run the front camera
https://app.box.com/s/xswdumrr4uqgbj5dczo9
Original thread : http://forum.xda-developers.com/showthread.php?t=2448962
remove FM radio ,its impossible without sources and sources = not possible because ST-Ericsson is no more
loren82 said:
good thread, try this, to run the front camera
https://app.box.com/s/xswdumrr4uqgbj5dczo9
Original thread : http://forum.xda-developers.com/showthread.php?t=2448962
Click to expand...
Click to collapse
Thank you but I have already a fix for front camera. He has published the patch before me so the credits go to him. I want give you a little spoiler: in order to fix from camera is necessary modify only 2 files .
Anyway i currently working on Wi-Fi direct, more suggests about this are well accepted .
percy_g2 said:
remove FM radio ,its impossible without sources and sources = not possible because ST-Ericsson is no more
Click to expand...
Click to collapse
I want investigate on these commits:
https://github.com/CyanogenMod/android_device_sony_montblanc-common/commit/52cedeea40957113358f92780d7f927414fcc73a
https://github.com/CyanogenMod/android_device_sony_montblanc-common/commit/0f86f877f07c7e9d9de7939012d0a19aa9ae2175
https://github.com/CyanogenMod/android_device_sony_montblanc-common/commit/61c4290fd4e7cadde9ff42c6fdf0161f6723f2e1
https://github.com/CyanogenMod/android_device_sony_montblanc-common/commit/8541f5b88cd05789b05ee1bf3034e17cb1c45b70
https://github.com/CyanogenMod/android_device_sony_montblanc-common/commit/59a6f62c4b4c65ba90a6bbac43c04010b1262d14
and maybe continue to develop this:
https://github.com/freexperia/android_packages_apps_FMRadio
hopefully reusing some code from MIUI FM Radio.
loren82 said:
good thread, try this, to run the front camera
https://app.box.com/s/xswdumrr4uqgbj5dczo9
Original thread : http://forum.xda-developers.com/showthread.php?t=2448962
Click to expand...
Click to collapse
While everyone is waiting for camera fix this one above works perfectly and fixes orientation or back camera, also led turns of after this flash when you have used the LED bar fix
@95A31 I guess you forgot to add the link to my guide in the op
Neurom707 said:
While everyone is waiting for camera fix this one above works perfectly and fixes orientation or back camera, also led turns of after this flash when you have used the LED bar fix
Click to expand...
Click to collapse
Front camera fix is coming in couple of days .
elia222 said:
@95A31 I guess you forgot to add the link to my guide in the op
Click to expand...
Click to collapse
Wops, fixed :good:.
95A31 said:
I want investigate on these commits:
https://github.com/CyanogenMod/andr...mmit/52cedeea40957113358f92780d7f927414fcc73a
https://github.com/CyanogenMod/andr...mmit/0f86f877f07c7e9d9de7939012d0a19aa9ae2175
https://github.com/CyanogenMod/andr...mmit/61c4290fd4e7cadde9ff42c6fdf0161f6723f2e1
https://github.com/CyanogenMod/andr...mmit/8541f5b88cd05789b05ee1bf3034e17cb1c45b70
https://github.com/CyanogenMod/andr...mmit/59a6f62c4b4c65ba90a6bbac43c04010b1262d14
and maybe continue to develop this:
https://github.com/freexperia/android_packages_apps_FMRadio
hopefully reusing some code from MIUI FM Radio.
Click to expand...
Click to collapse
If you can get FM audio enabled, there should be enough open source code out there for an open source FM app. The closed source libfmradio.cg2900.so would be needed, but should still work.
An ambitious person might even be able to get FM transmit working on some Euro phones. I was able to enable it with my app, but couldn't figure out how to enable FM transmit audio with some quick attempts.
mikereidis said:
If you can get FM audio enabled, there should be enough open source code out there for an open source FM app. The closed source libfmradio.cg2900.so would be needed, but should still work.
An ambitious person might even be able to get FM transmit working on some Euro phones. I was able to enable it with my app, but couldn't figure out how to enable FM transmit audio with some quick attempts.
Click to expand...
Click to collapse
When I will start to work on the FM radio, I would be happy to collaborate with you .
Fix front camera (Fixed here by @xx214718247):
Also this fix consist in use right camera files as FreeXperia use the Xperia GO version. The right files can be downloaded from here and here. The first one is necessary in order to make able the system to recognize front camera, the second allow to use it. After have substituted the files in relative CyanogenMod's build folders, recompile and flash.
Good to see ambitious devs like you creating xperia u's future!
SIGNATURE OUTDATED. I now use honami moonwalker 4.2
In this period I am looking Team Canjica's camcorder fix:
In this post @DevSwift1 suggest to use android_vendor_sony by Team Canjica for fix camcorder.
It work, but it broke bluethoot. This small issue can be fixed reverting this commit.
The two main differences between Team Canjica's version and TheMuppets' version are:
Different organization of common and device specific libs.
Team Canjica version require that some media and camera libs shoud be compiled from source.
If kumquat-vendor-blobs.mk is modified in order to require that the media and camera libs must be compiled frome source we obtain a lenght 0:00 video and logcat report an error of OMX node allocation about h264enc.
TODO: Search which other differents files are involved in recording/encoding process in order to make TheMuppets' version work.
Currently I am also investigate on Wi-Fi tethering/direct:
For fix these issues I follow this guide by Texas Instruments. The firts issue that I have found is broken Wi-Fi. This can be simply fixed setting the right permissions to files and directories involved in Wi-Fi as described here. The second problem is of corse tethering. The first issue is in hostapd.conf: when Hostapd try to change the owner of the control interface as described in line 8 give a operation not permitted error. The (naive) solution is eliminate line 8 so Hostapd can run without problem. The second and critical issue concern how softAP is used by the system. Below the interesting logcat's part:
Code:
...
E/hostapd ( 2731): Configuration file: /data/misc/wifi/hostapd.conf
...
E/hostapd ( 2731): Using interface wlan0 with hwaddr 01:23:45:67:89:AB and ssid 'AndroidAP'
D/hostapd ( 2731): Deriving WPA PSK based on passphrase
D/SoftapControllerTI( 1484): hostapd started OK
D/SoftapControllerTI( 1484): hostapd set - Ok
E/NetdConnector( 1967): NDC Command {14 softap set wlan0 wl0.1 AndroidAP wpa2-psk trolololol} took too long (1823ms)
D/hostapd ( 2731): random: Got 20/20 bytes from /dev/random
D/hostapd ( 2731): WPA: Delay group state machine start until Beacon frames have been configured
E/hostapd ( 2731): Failed to setup control interface
E/hostapd ( 2731): wlan0: Unable to setup interface.
...
TODO: Search documentation about SoftAP in order to make tethering work.
About Wi-Fi direct the issues start to be hard to fix. From ICS to JB is changed more about Wi-Fi direct managing, in detail JB require a network device called p2p0 in order to get working Wi-Fi direct. AFAIK this device is created and managed only in recents verions of wpa_supplicant and not all drivers can handle this kind of device.
TODO: Porting CM10.2 version of wpa_supplicant in order to make Wi-Fi direct work.
mmm
++++
Hi guys,
here I created a git repository with all fixes that I analized. In order to exploit it just simply download it as zip archive and extract the content over the CyanogenMod's build folder.
I hope in a tethering fix.
Thx for the repo.
Inviato dal mio Xperia U con Tapatalk
For led bar u can use dis..
http://forum.xda-developers.com/showthread.php?t=2429318
marce78 said:
I hope in a tethering fix.
Thx for the repo.
Inviato dal mio Xperia U con Tapatalk
Click to expand...
Click to collapse
I'm working on
ajain3982 said:
For led bar u can use dis..
http://forum.xda-developers.com/showthread.php?t=2429318
Click to expand...
Click to collapse
Thank you :good:
Hi guys, tethering fix is not so easy as I image. I think that @munjeni in this porting have the same problem. Probably is enought a good configuration but without documentation is very hard. I ask you provide to me this files:
init.st-ericsson.rc form Stock Jelly Bean Xperia GO
A logcat from Stock Jelly Bean Xperia GO when Wi-Fi tethering is turn on
Daily report:
Camcorder: For fix this, I decide to use TeamCanjica's android_vendor_sony because it is updated and I prefer his "old" organization of common and device specific files. It already contain the back camera fix, so is useless keep it as different fix. A side effect is broken bluetooth, that as I previous say can be fixed reverting this commit. I fond also iw broken so I used the ICS version.
Wi-Fi thetering: I keep working on this but I dont see the end (for now ). In detail the jellybean Android Network Deamon not has full support for SoftAP used by FreeXperia. The support was reintroduced in this commit. The TeamCanjica has ported this fix in the own Android Network Deamon so I use this last one. I try several configuration of hostapd.conf but none seams work.
@95A31, appreciate doing this and sorry for intruding but it seems that you're the only one looking at real problems right now. Anyway, to the point.
There seems to be everlasting problem of extreme call dialer lag in jb roms, at least in ones that I've tried. During the answering of call phone just freezes and hangs for a period of time during which call gets established but you can't hear or be heard. Lots of people are not using jb especially because of this. However, I haven't tried cm10 in a while 'cause fxp stopped updating it and I don't have enough knowledge to build it, so I can't say if it's present there. So if you think you might be able to fix the dialer please try it. And also if you're already building cm10 with fixes feel free to upload it somewhere, I'm sure people would flash it. That way you could get some more logcats. Of course, I'm just suggesting stuff, there's no pressure and it all depends on if you have free time.
Thanks
Dialer lag affects me only after 3 months of jb. Thereafter, i change roms and wipe data amd to its not there
Sent from my LT22i using xda premium
Hi,
I have been porting a development board YSE5250 to kitkat. I already have JB and it's working fine on board.
I followed few articles available on XDA and ported the board to AOSP Kitkat source code. I am using JB kernel with ported android. Now my device boots up and mounts different partitions properly. I have access to adb shell. I can see in build.prop that the build properties are as per I set during building AOSP KK.
But, the display is not coming up. While looking through logcat I can see that surfaceflinger dies due to some error. Due to this other services also dies. I am not able to locate exact cause of error.
I am attaching three files, build properties, logcat and dmesg.
Any direction to resolve this issue will be great help.
Thanks,
Sunil.
which guide u used while porting
I have jellybean android running on my device
The problem is i want to do it kitkat by porting another mobile stockrom official
Mine is mt6572 and port rom is mt6582
Suggest me any guide and kitkat roms for mt6572
I'm trying to compile Android 4.2.2 for the Lenovo A2109A. AOSP 4.1.2 mostly worked out fine, except that panorama mode for the camera didn't work. In AOSP 4.2.2 the camera HAL didn't seem to connect to the camera, so I switched to CM-10.1. Camera HAL loads fine, but it doesn't take pictures. The problem seems to be that the stock camera HAL is linked to a version of libjpeg with proprietary additions from nvidia and I can't figure out what they are. Someone else was able to successfully compile CM-10.1 with a working camera by using libjpeg-turbo for compilation (see here), but it also needs a patch for skia that I can't find.
So right now I'm basically stuck and I'm looking for different ways forward. I could really use your advice. Should it be possible to use the camera hal from a related device instead? I know that the nexus 7 is also a tegra3 device, and very close to A2109. It does use different camera devices, but these can be configured in nvcamera.conf. I used strings to find whether any proprietary lib referenced the specific cameras and I found only one, libnvodm_imager.so. The most important differences appear to be in the kernel source, in the following files:
drivers/media/video/tegra/tegra_camera.c
drivers/media/video/tegra/tegra_dtv.c
My question--to what extent should it be possible to just use the grouper tegra camera files for the kernel and then use the grouper camera HAL? Or do you have a different suggestion for me to proceed? I'm asking because I can hardly code. I am, however, getting better and better with git and patches, and I did manage to fix two compile issues in the lenovo kernel source.
My kernel source is over here. My device tree is over here (defaults to aosp 4.2.2 branch, cm-10.1 is a different branch). Grouper kernel sources are over here.
P.S., I have a development thread over at androidtablets.net, which also contains various details.
Answering my own post...
I tried using grouper HAL, gives error message. But using tf700 camera HAL worked, when used with tf700 libnvcamerahdr.so, both taken from stock 4.2.
So--problem solved
So,
After years i managed to get kernel working now my question would be what are the modifications to the kernel needed to enabled Camera 2 API Support.
It would be great if someone would provide me A Github Repo (Kernel Sources) which has Camera 2 API Enabled .
Its my first time working with kernels lol
Thanks anyways
The Whole camera releated libraries/binaries on ROM and on kernel.
In short, if you're not pro-developer, you can't do that.