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
Hello,
Does someone know if rom makers actually fix bugs in the Android source code? for example, can the bugs presented in android 5.0 be fixed by Cyanogen or do they have to wait for Google to release a new version?
I recently read about a memory leak in Android 5.0, and I'm running CM12 nightly and i haven't experienced any memory leak, did CM fix that?
Yes, they often are able to and do fix bugs. Occasionally Google or other manufacturers use fixes from the community. But often times the normal rom maker is more of a maintainer - just building from Source for a particular device and need to wait till the commits are pushed to the source code before the rom makers can add to a particular device.
es0tericcha0s said:
Yes, they often are able to and do fix bugs. Occasionally Google or other manufacturers use fixes from the community. But often times the normal rom maker is more of a maintainer - just building from Source for a particular device and need to wait till the commits are pushed to the source code before the rom makers can add to a particular device.
Click to expand...
Click to collapse
Great answer, thank you!
es0tericcha0s said:
Yes, they often are able to and do fix bugs. Occasionally Google or other manufacturers use fixes from the community. But often times the normal rom maker is more of a maintainer - just building from Source for a particular device and need to wait till the commits are pushed to the source code before the rom makers can add to a particular device.
Click to expand...
Click to collapse
Good to know, thanks!
Recently i have ported a cm12.1 beta 7 stable v2 rom
Everything is working fine except for front camera & Bluetooth
Plz can anyone know how to fix this?
I have tried many lib files, but non of them r working
Plz help on it to fix this issue
Anyone plz
Your issue is gonna be a kernel issue and without the source there is nothing you can do. It is a common issue with devices running that chip set. That's why developers don't touch devices with it.
zelendel said:
Your issue is gonna be a kernel issue and without the source there is nothing you can do. It is a common issue with devices running that chip set. That's why developers don't touch devices with it.
Click to expand...
Click to collapse
My phone is Symphony h150. Its mediatek mt6582 chipset.
I don't know about any source file. But i think not.
So ur telling me that there's no way
rabin69x said:
My phone is Symphony h150. Its mediatek mt6582 chipset.
I don't know about any source file. But i think not.
So ur telling me that there's no way
Click to expand...
Click to collapse
Yes I'm saying that without a proper kernel then there will be things that just can't be fixed. Normally things like the camera and wifi radios. You might be able to hack your way through it but it will take weeks of searching through the code.
The kernel source code is the base code that is required by law to be published for any device that runs a Linux kernel (any android device) the issue with that chip set is they are based in China and dont respect copyright laws or the GPL.
rabin69x said:
My phone is Symphony h150. Its mediatek mt6582 chipset.
I don't know about any source file. But i think not.
So ur telling me that there's no way
Click to expand...
Click to collapse
If it's still actual for you (2 years, but still...), mediatek has laid off some kernel and AOSP sources for mt65xx series. Also check out this repo: github.com /bq/aquaris-E5, it has some code for your chip and other Mediatek stuff.
Also you have few other options:
Build your ROM around existing (official) kernel, adding more drivers as .ko's. I've had certain success adding some USB drivers like that.
Use some .so's from your original ROM. Sometimes manufacturers don't provide sources for libcamera.so/libcamera_client.so (camera), libhardware.so/libhardware_legacy.so (wifi and some minor stuff, like vibromotor)
Hi. I am happy that my old Smultron is not dead yet.
Due to its small size, I would like to reactivate it as a bicycle computer / fitness tracker. The apps that I usually use require Lollipop as a minimum.
I seem to remember that I half-heartedly tried the same already about a year ago, but did not succeed with installing the ANT+ services from the Playstore.
Currently, I am at CM13.
Now I found that in the AOKP FAQ, it is stated:
Q: Why is ANT+ not working?
A: ANT+ developers do not support our wifi chip (wl1271) beyond JB 4.1. ANT+ will never work except if we write the needed source code changes from scratch.
That leads me to the qestion: Is this true for all ROMs, or just AOKP? Or more in general: Which ROMs supports ANT+?
Umm... noone knows this?
a-dummy said:
Umm... noone knows this?
Click to expand...
Click to collapse
All Stock based GB and ICS ROMs afaik.
Dunno about JB and KK ROMs