Related
Hi All
Today I found a combination (which might have been out there for a while) how the Camera actually is working for Topaz Android
1. Download the FRX04 version
2. http://forum.xda-developers.com/showthread.php?t=883966 check there for section "Topaz Users"
3. Don't forget the post "[23/01/2011] :" to dissable 2 rows in froyo.conf file
The Camera was able to startup and I took one Picture
The speed of the Cam.. well.. don't be to happy.. but it is working anyway
/olme
Yeah,works fine, but only 3 MP and without auto-focus,but it works more quick than im windows mobile.
Oh,but programm(name forgotten) in FRX04 for Rhodium(23.01.11) is more usable,you can make photo by pressing on volume keys
yes indeed WinMo is quicker.. but one step at the time This is the first time I ever on my Topaz and Android was able to even see that it was "connected" and that I could take a picture.
The next development will be that the rest of the goodies will appear such as speed and autofocus etc etc..
GOOD job Android Devs!
/olme
Please, keep in mind that it's in debug state, a branch of XDAndroid code made by viruscrazy.
If you want to help test it, follow the instructions in the first post and leave your logs there.
Thanks.
Somebody tested camera on FRX04(23.01.11)?
saneksem said:
Somebody tested camera on FRX04(23.01.11)?
Click to expand...
Click to collapse
yes with provided topaz test kernel it's working till 3mp pictures
@5mp camera crashed... but this is allready known and developer asked for dmesg log files to finetune the driver...
-bl4ckb1rd
p.s. camera driver did not work with latest 01253 kernel
can any1 pls upload the conf file? because i couldn't find the 2 rows......
[23/01/2011] :
Updated Lib_package to fix the froyo.user.conf file (thanks to arrrghhh again, you're the "conf file" specialist) and the Blackstone picture crash (I hope...). If you are using latest FRX04 build and rootfs, you may have to disable the two following lines (add a "#" at the begginnning of the line) :
Code:
mount --bind /sdcard/lib_camera/libGLES_qcom.so /system/lib/egl/libGLES_qcom.so
mount --bind /sdcard/lib_camera/gralloc.msm7k.so /system/lib/hw/gralloc.msm7k.so
Could DEVs add camera to Gingerbread?
There is a new fix for 5MP. It works. You need the Kernel from 28.01.11 and the new attached Haret Version. Do not use the attached kernels and don't forget to write the line:
set INITRD_OFFSET 0x608000
under "set initrd initrd.gz" (Startup.txt)
http://forum.xda-developers.com/showthread.php?t=883966
CameraWorks
Erikson89 said:
There is a new fix for 5MP. It works. You need the Kernel from 28.01.11 and the new attached Haret Version. Do not use the attached kernels and don't forget to write the line:
set INITRD_OFFSET 0x608000
under "set initrd initrd.gz" (Startup.txt)
http://forum.xda-developers.com/showthread.php?t=883966
Click to expand...
Click to collapse
I also confirm it works
Here it doesn't. New haret makes the topaz reboot in winmo...
Well, it doesn't seem to work with Froyo X...
What doesn't seems to work?
The Camera is working but as the forum said.. only stable up to 3Mpixels...
olme said:
Hi All
Today I found a combination (which might have been out there for a while) how the Camera actually is working for Topaz Android
1. Download the FRX04 version
2. http://forum.xda-developers.com/showthread.php?t=883966 check there for section "Topaz Users"
3. Don't forget the post "[23/01/2011] :" to dissable 2 rows in froyo.conf file
The Camera was able to startup and I took one Picture
The speed of the Cam.. well.. don't be to happy.. but it is working anyway
/olme
Click to expand...
Click to collapse
Place a files hire!
Brain-brick with your link
sorry I don't understand what you want me to do..
Do you want me to place a link to my files I used to get the Camera running or what?
cheers
/Olme
olme said:
sorry I don't understand what you want me to do..
Do you want me to place a link to my files I used to get the Camera running or what?
cheers
/Olme
Click to expand...
Click to collapse
Yes! Yes and Yes!
check this link where I have uploaded my andboot.
1. Download it and extraxt it anywhere
2. put the 2 folders on the root of your SD Card.
3. Start Haret.exe
hotfile .com /dl/101065742/b00ae64/andboot.rar.html
Thanks for you effort uploading the file
I think someone needs to thank you also , but i think he's "cooking" right now
olme said:
check this link where I have uploaded my andboot.
1. Download it and extraxt it anywhere
2. put the 2 folders on the root of your SD Card.
3. Start Haret.exe
hotfile .com /dl/101065742/b00ae64/andboot.rar.html
Click to expand...
Click to collapse
wow
thx, cam is working for me, but only up to 2 Mpix,
but in this version wifi error after reconnect... :-(
yes i think cooking can be started ;-)
I have downloaded and flashed the latest versions of both CM10.1 AND LiquidSmooth. The rom is smoothand fast and as far as I have used it, only encountered little bugs here and there that I don't really care about. However the Camera still doesn't function for me. I know this was fixed in like the second release of cm10.1 but for me the camera still isn't working with the latest release. it gives me the error message 'cant connect to camera' I live in Singapore and thus my phone is from singtel. maybe its different for phones in Sg? and I would be more than happy to give a logcat if someone told me how to thank you so muchhh ) Finally I can get rid of touchwiz
Sv: Camera Problem With CM10.1 AND LiquidSmooth S3 i9305 (with the latest versions)
ebenezer57 said:
I have downloaded and flashed the latest versions of both CM10.1 AND LiquidSmooth. The rom is smoothand fast and as far as I have used it, only encountered little bugs here and there that I don't really care about. However the Camera still doesn't function for me. I know this was fixed in like the second release of cm10.1 but for me the camera still isn't working with the latest release. it gives me the error message 'cant connect to camera' I live in Singapore and thus my phone is from singtel. maybe its different for phones in Sg? and I would be more than happy to give a logcat if someone told me how to thank you so muchhh ) Finally I can get rid of touchwiz
Click to expand...
Click to collapse
Can you even start the camera? What do you do when you get the error?
Sent from my GT-I9305 using xda app-developers app
ebenezer57 said:
I have downloaded and flashed the latest versions of both CM10.1 AND LiquidSmooth. The rom is smoothand fast and as far as I have used it, only encountered little bugs here and there that I don't really care about. However the Camera still doesn't function for me. I know this was fixed in like the second release of cm10.1 but for me the camera still isn't working with the latest release. it gives me the error message 'cant connect to camera' I live in Singapore and thus my phone is from singtel. maybe its different for phones in Sg? and I would be more than happy to give a logcat if someone told me how to thank you so muchhh ) Finally I can get rid of touchwiz
Click to expand...
Click to collapse
Reboot your phone (to remove irrelevant data), go onto Mobile Terminal (if you don't have it download it) then login as root 'su', then cd to a new directory (recommend downloads or something) so 'cd /storage/emulated/legacy/Download' and then run 'logcat > cannot_connect_to_camera_logcat.txt', hope screen it (let it run in the background) and try open up the camera app. It will give you the error as usual but then you want to exit out of the camera app, go back into mobile terminal and close the session (the big 'X' in the top right corner).
Then get the file off your device, upload it to http://pastebin.com/ and put a link in the Liquid Smooth thread and the Cyanogenmod thread (although Cyanogenmod doesn't have a maintainer so it is less likely to be fixed there but the fix should work across roms).
Also use the -v long output and tags to make reading logcats much easier and for more relevant information (*W tag for warnings only etc.) so it would be 'logcat *W -v long > ...'
sebbe312 said:
Can you even start the camera? What do you do when you get the error?
Sent from my GT-I9305 using xda app-developers app
Click to expand...
Click to collapse
Yeap i can, it goes to the app and gives me the error. i just press home and close it.
I have posted on the LiquidSmooth thread in the development section and attatched the log file as well
Magik_Breezy said:
Reboot your phone (to remove irrelevant data), go onto Mobile Terminal (if you don't have it download it) then login as root 'su', then cd to a new directory (recommend downloads or something) so 'cd /storage/emulated/legacy/Download' and then run 'logcat > cannot_connect_to_camera_logcat.txt', hope screen it (let it run in the background) and try open up the camera app. It will give you the error as usual but then you want to exit out of the camera app, go back into mobile terminal and close the session (the big 'X' in the top right corner).
Then get the file off your device, upload it to http://pastebin.com/ and put a link in the Liquid Smooth thread and the Cyanogenmod thread (although Cyanogenmod doesn't have a maintainer so it is less likely to be fixed there but the fix should work across roms).
Also use the -v long output and tags to make reading logcats much easier and for more relevant information (*W tag for warnings only etc.) so it would be 'logcat *W -v long > ...'
Click to expand...
Click to collapse
Thanks for the instructions! I found this app to do the recording for me though and i have uploaded the logcat with the tag on the liquid smooth thread
-- I've accidentally posted this in the i9300 QA forum so I'm moving it here since it's the same issue --
Hi, I'm trying to setup an AOSP rom for my brother on his i9305 and everything is working great for the latest CM build but the camera app cannot start saying it cannot connect to camera:
02-16 02:37:04.725: E/SecCameraHardware(1951): camFW = GHFJ02
02-16 02:37:04.725: E/SecCameraHardware(1951): FimcV4l2 init: error -1, VIDIOC_S_INPUT
02-16 02:37:04.725: E/SecCameraHardware(1951): initCamera X: error, /dev/video0
02-16 02:37:04.725: V/SecCameraHardware(1951): FimcV4l2 deinit EX
02-16 02:37:04.725: E/SecCameraHardware(1951): createInstance: error, camera cannot be initialiezed
02-16 02:37:04.725: E/SecCameraHardware(1951): Instance is not created
02-16 02:37:04.725: E/CameraWrapper(1951): vendor camera open fail
02-16 02:37:04.725: E/CameraClient(1951): Could not open camera 0: -38
02-16 02:37:04.725: E/CameraClient(1951): initialize: Camera 0: unable to initialize device: Function not implemented (-38)
02-16 02:37:04.725: I/CameraClient(1951): Destroying camera 0
02-16 02:37:04.730: E/CameraHolder(3885): fail to connect Camera
02-16 02:37:04.730: E/CameraHolder(3885): java.lang.RuntimeException: Fail to connect to camera service
02-16 02:37:04.730: E/CameraHolder(3885): at android.hardware.Camera.native_setup(Native Method)
02-16 02:37:04.730: E/CameraHolder(3885): at android.hardware.Camera.<init>(Camera.java:340)
02-16 02:37:04.730: E/CameraHolder(3885): at android.hardware.Camera.open(Camera.java:302)
02-16 02:37:04.730: E/CameraHolder(3885): at com.android.camera.CameraManager.cameraOpen(Camera Manager.java:283)
02-16 02:37:04.730: E/CameraHolder(3885): at com.android.camera.CameraHolder.open(CameraHolder. java:210)
02-16 02:37:04.730: E/CameraHolder(3885): at com.android.camera.Util.openCamera(Util.java:366)
02-16 02:37:04.730: E/CameraHolder(3885): at com.android.camera.PhotoModule$CameraStartUpThread .run(PhotoModule.java:323)
Now, the camera firmware version GHFJ02 is nothing like any I've been able to come across (none start with GH****) and have seen that changing the firmware can help with this problem. Does anyone know if it would be ok for me to install (downgrade as I could figure from the letters - revisions) a differently labeled firmware like for instance GDFE01 which (mostly) works ok with CM? Also, is it possible to backup the current firmware so I can restore it in case of problems? I see a dump firmware option but dont have a clue where this dump ends up being stored.
Also, if someone can give any more info on the above error message and what exactly does it mean? Maybe I can help in fixing the camera interface if it's possible.
Since it's such a crucial part of the phone, either I get it working somehow or he's better of with a rooted stock rom.
Thanks
mm43107 said:
-- I've accidentally posted this in the i9300 QA forum so I'm moving it here since it's the same issue --
Hi, I'm trying to setup an AOSP rom for my brother on his i9305 and everything is working great for the latest CM build but the camera app cannot start saying it cannot connect to camera:
02-16 02:37:04.725: E/SecCameraHardware(1951): camFW = GHFJ02
02-16 02:37:04.725: E/SecCameraHardware(1951): FimcV4l2 init: error -1, VIDIOC_S_INPUT
02-16 02:37:04.725: E/SecCameraHardware(1951): initCamera X: error, /dev/video0
02-16 02:37:04.725: V/SecCameraHardware(1951): FimcV4l2 deinit EX
02-16 02:37:04.725: E/SecCameraHardware(1951): createInstance: error, camera cannot be initialiezed
02-16 02:37:04.725: E/SecCameraHardware(1951): Instance is not created
02-16 02:37:04.725: E/CameraWrapper(1951): vendor camera open fail
02-16 02:37:04.725: E/CameraClient(1951): Could not open camera 0: -38
02-16 02:37:04.725: E/CameraClient(1951): initialize: Camera 0: unable to initialize device: Function not implemented (-38)
02-16 02:37:04.725: I/CameraClient(1951): Destroying camera 0
02-16 02:37:04.730: E/CameraHolder(3885): fail to connect Camera
02-16 02:37:04.730: E/CameraHolder(3885): java.lang.RuntimeException: Fail to connect to camera service
02-16 02:37:04.730: E/CameraHolder(3885): at android.hardware.Camera.native_setup(Native Method)
02-16 02:37:04.730: E/CameraHolder(3885): at android.hardware.Camera.<init>(Camera.java:340)
02-16 02:37:04.730: E/CameraHolder(3885): at android.hardware.Camera.open(Camera.java:302)
02-16 02:37:04.730: E/CameraHolder(3885): at com.android.camera.CameraManager.cameraOpen(Camera Manager.java:283)
02-16 02:37:04.730: E/CameraHolder(3885): at com.android.camera.CameraHolder.open(CameraHolder. java:210)
02-16 02:37:04.730: E/CameraHolder(3885): at com.android.camera.Util.openCamera(Util.java:366)
02-16 02:37:04.730: E/CameraHolder(3885): at com.android.camera.PhotoModule$CameraStartUpThread .run(PhotoModule.java:323)
Now, the camera firmware version GHFJ02 is nothing like any I've been able to come across (none start with GH****) and have seen that changing the firmware can help with this problem. Does anyone know if it would be ok for me to install (downgrade as I could figure from the letters - revisions) a differently labeled firmware like for instance GDFE01 which (mostly) works ok with CM? Also, is it possible to backup the current firmware so I can restore it in case of problems? I see a dump firmware option but dont have a clue where this dump ends up being stored.
Also, if someone can give any more info on the above error message and what exactly does it mean? Maybe I can help in fixing the camera interface if it's possible.
Since it's such a crucial part of the phone, either I get it working somehow or he's better of with a rooted stock rom.
Thanks
Click to expand...
Click to collapse
Are you from sg? cuz I think ppl in sg have this problem. Anyway u should post this on the development thread! ull get a lot more help there. but I think u cant post there yet because u only have 3 posts so just post something 7 more times and come to the development thread in the liquidsmooth thread! ill copy ur message there and ill let u know the response? come on there as soon as u can!
ebenezer57 said:
Are you from sg? cuz I think ppl in sg have this problem. Anyway u should post this on the development thread! ull get a lot more help there. but I think u cant post there yet because u only have 3 posts so just post something 7 more times and come to the development thread in the liquidsmooth thread! ill copy ur message there and ill let u know the response? come on there as soon as u can!
Click to expand...
Click to collapse
Don't bother putting it on the thread. Email logcats directly to [email protected] & [email protected].
Sent from my GT-I9305 using xda premium
Well done just like a turkey with correct gran mah...lolxxx
Magik_Breezy said:
Don't bother putting it on the thread. Email logcats directly to [email protected] & [email protected].
Sent from my GT-I9305 using xda premium
Click to expand...
Click to collapse
Yeap I sent them a email right after I saw amp's post.
ebenezer57 said:
Are you from sg? cuz I think ppl in sg have this problem. Anyway u should post this on the development thread! ull get a lot more help there. but I think u cant post there yet because u only have 3 posts so just post something 7 more times and come to the development thread in the liquidsmooth thread! ill copy ur message there and ill let u know the response? come on there as soon as u can!
Click to expand...
Click to collapse
I'm from croatia (hr), maybe our operator is shipping phones from sg
I know I'd be better off posting in the dev forum, but have to pass the 10 post min. like you figured...
PS
Whose emails are these ([email protected] & [email protected])? Is there any more info I can send them to help? dmesg log?
ebenezer57 said:
I have downloaded and flashed the latest versions of both CM10.1 AND LiquidSmooth. The rom is smoothand fast and as far as I have used it, only encountered little bugs here and there that I don't really care about. However the Camera still doesn't function for me. I know this was fixed in like the second release of cm10.1 but for me the camera still isn't working with the latest release. it gives me the error message 'cant connect to camera' I live in Singapore and thus my phone is from singtel. maybe its different for phones in Sg? and I would be more than happy to give a logcat if someone told me how to thank you so muchhh ) Finally I can get rid of touchwiz
Click to expand...
Click to collapse
I'm also from SG and using 9305, though i didn't have this camera issue, I noticed that the camera seems stretched in video mode. I also noticed that 4G(singtel) is not as great as the stock rom, I used to have full 4G signal here at home but now I can only get 3G, my visitors who have i9305 also gets good 4G signal here. But I can get good 4G signal from other places. Besides these issues, everything looks great. It's a very good job done by Amplified(Liquid Team) and codeworkx for the CM10.1.
mm43107 said:
I'm from croatia (hr), maybe our operator is shipping phones from sg
I know I'd be better off posting in the dev forum, but have to pass the 10 post min. like you figured...
PS
Whose emails are these ([email protected] & [email protected])? Is there any more info I can send them to help? dmesg log?
Click to expand...
Click to collapse
I believe the Singapore version also uses the same international version i9305
deepsweech said:
I'm also from SG and using 9305, though i didn't have this camera issue, I noticed that the camera seems stretched in video mode. I also noticed that 4G(singtel) is not as great as the stock rom, I used to have full 4G signal here at home but now I can only get 3G, my visitors who have i9305 also gets good 4G signal here. But I can get good 4G signal from other places. Besides these issues, everything looks great. It's a very good job done by Amplified(Liquid Team) and codeworkx for the CM10.1.
Click to expand...
Click to collapse
Your signal has absolutely nothing to do with the ROM unless your ROM flashed your modem too and CM and LS both don't so there should be absolutely no difference unless you have made a standalone decision to flash a different modem. Constructive criticism, sorry if I came across as rude.
Sent from my GT-I9305 using xda premium
mm43107 said:
I'm from croatia (hr), maybe our operator is shipping phones from sg
I know I'd be better off posting in the dev forum, but have to pass the 10 post min. like you figured...
PS
Whose emails are these ([email protected] & [email protected])? Is there any more info I can send them to help? dmesg log?
Click to expand...
Click to collapse
They are part of the team liquid! (developers of the liquidsmooth rom) yeap u can send them any more info that u think would be helpful!
deepsweech said:
I'm also from SG and using 9305, though i didn't have this camera issue, I noticed that the camera seems stretched in video mode. I also noticed that 4G(singtel) is not as great as the stock rom, I used to have full 4G signal here at home but now I can only get 3G, my visitors who have i9305 also gets good 4G signal here. But I can get good 4G signal from other places. Besides these issues, everything looks great. It's a very good job done by Amplified(Liquid Team) and codeworkx for the CM10.1.
Click to expand...
Click to collapse
Ahh... so its just my phone then. damn that sucks. ill try doing a full wipe and reflashing! hopefully that fixes the problem!
Edit: I did a full wipe including system but no luck ):
Magik_Breezy said:
Your signal has absolutely nothing to do with the ROM unless your ROM flashed your modem too and CM and LS both don't so there should be absolutely no difference unless you have made a standalone decision to flash a different modem. Constructive criticism, sorry if I came across as rude.
Sent from my GT-I9305 using xda premium
Click to expand...
Click to collapse
all good bro, im also a noob in this AOSP thing. Ok ill just search for the best modem flash.
You're not the only one.
I'm having the same issue.
if you've found some solution, can you tell me?
Hi, I just got my GT-19305 and rooted as soon as I got it. I get the same error when opening the camera app "can't connect to camera". I have tried Cyanogenmod stable, and some nightlies, CodenameLungo and RipperROM (the camera works on this one).
I have tried searching for an answer for two days now but I cant find anything helpfull.
I got my phone in Norway btw.. (which is where I live)..
Any news ?
Little up ?
Unofficial CyanogenMod 10.1
Rom: Unofficial CyanogenMod 10.1
Android version: 4.2.2
Status: Alpha (means not ready as beta or even stable release!)
What doesn't work:
Sound partially, only calls not working right
Wifi
GPS
Bluetooth
Brightness control
Airplane mode
Camera, did work though in earlier version
Disclaimer
I am not responsible for bricked devices, broken hearts, thermonuclear war or you getting fired because the alarm app failed. It's up to you, not to me.
Click to expand...
Click to collapse
Downloads:
Google Drive CM10.1
Mirror, hosted by Burn02
The version differences:
Code:
24/2/14
[LIST]
[*] Using new audio hall
[*] Microphone works now, call still doesn't
10/2/14
[LIST]
[*] Initial audio support
[*] Fixed Wifi symlink for MAC-adres
[*] ICS_AUDIO_BLOB disabled
[/LIST]
01/12/13
[LIST]
[*] ICS_AUDIO_BLOB enabled
[*] Using original audio blobs
[/LIST]
14/11/13
[LIST]
[*] Both Internal storage and external storage working
[*] Build modified init from source
[*] Dalvik with x86 houdini support
[*] More modules build from source
[/LIST]
6/11/13
[LIST]
[*] Only internal storage working
[*] Libc with x86 wrappers support
[*] Pixelflinger/charger with x86 encoder support
[*] Ramdisk changes
[*] Android Build fixes for x86
[*] Add intel specific codes
[/LIST]
Workarounds:
The Rom can bootloop when installed in TWRP. If so use CWM instead for a while till TWRP is working correctly.
Want to help?
This Rom is made by many people that contribute to it, if it is in code, new information or just bug logs. Everybody can help. Make a 'Logcat' about the problems u encounter and post them here. Give a brief explanation of what u did and wanted to archive (we will try our best to get them sorted, eventually) or contribute with code into my github at the moment.
Click to expand...
Click to collapse
Source:
https://www.github.com/HazouPH
About the sound:
When using the rom zip with ICS_BLOBS_ENABLED and adding the right files:
etc/parameter-framework/*
etc/sound.conf
etc/audio_effects.conf
etc/media_codecs.xml
etc/phonecall_es305b_*
lib/hw/alsa.smi.so
lib/hw/audio.primary.smi.so
lib/hw/audio_policy.smi.so
lib/parameter-framework-plugins/*
lib/libasound.so
usr/lib/alsa-lib/*
usr/share/alsa/*
The rom will bootloop and the mediaserver will crash with a log file. See attachment. If u have any idea on how to solve it, i would happily like to know.
Hazou said:
About the sound:
When using the rom zip with ICS_BLOBS_ENABLED and adding the right files:
etc/parameter-framework/*
etc/sound.conf
etc/audio_effects.conf
etc/media_codecs.xml
etc/phonecall_es305b_*
lib/hw/alsa.smi.so
lib/hw/audio.primary.smi.so
lib/hw/audio_policy.smi.so
lib/parameter-framework-plugins/*
lib/libasound.so
usr/lib/alsa-lib/*
usr/share/alsa/*
The rom will bootloop and the mediaserver will crash with a log file. See attachment. If u have any idea on how to solve it, i would happily like to know.
Click to expand...
Click to collapse
Good work Hazou !
I will give you some idea. And why don't you use JB libs ?
1. Replace mediaserver by ICS one
2. Replace /system/lib/hw/audio.primary.smi.so by CyanogenMod file
3. There is a problem with libc.so, so just try to replace this lib with ICS one....
4. Replace /system/lib/libat-manager.so (if exist) by CM one
Do these steps one by one and logcat for each step.
GalaxyUser
GalaxyUser said:
Good work Hazou !
I will give you some idea. And why don't you use JB libs ?
1. Replace mediaserver by ICS one
2. Replace /system/lib/hw/audio.primary.smi.so by CyanogenMod file
3. There is a problem with libc.so, so just try to replace this lib with ICS one....
4. Replace /system/lib/libat-manager.so (if exist) by CM one
Do these steps one by one and logcat for each step.
GalaxyUser
Click to expand...
Click to collapse
Ty, for the suggestions. Some i can already answer
1. We could try this, but then also the libaudioflinger needs replacing. And maybe another file.
2. Can try it, but most likely doesn't work. The stock cyanogenmod one doesn't have the right code the execute our soundcard. I found out that the audio_policy.smi.so is the stock one with just small modifications.
3. Libc can't be switched. To many things depend on libc. And besides that, the code in libc were it goes wrong is the same one as my modified jb libc
4. libat-manager is a specific module for our device. we don't have the right sources to build it. But i can maybe replace it with the one from the 4.2.2 drop of the chineze version. But then it has some restrictions because off the chinese firewall.
Keep up the ideas. Maybe we get there someday
Hazou
Hazou said:
Ty, for the suggestions. Some i can already answer
1. We could try this, but then also the libaudioflinger needs replacing. And maybe another file.
2. Can try it, but most likely doesn't work. The stock cyanogenmod one doesn't have the right code the execute our soundcard. I found out that the audio_policy.smi.so is the stock one with just small modifications.
3. Libc can't be switched. To many things depend on libc. And besides that, the code in libc were it goes wrong is the same one as my modified jb libc
4. libat-manager is a specific module for our device. we don't have the right sources to build it. But i can maybe replace it with the one from the 4.2.2 drop of the chineze version. But then it has some restrictions because off the chinese firewall.
Keep up the ideas. Maybe we get there someday
Hazou
Click to expand...
Click to collapse
Thanks for answer.
1. Try to replace libaudioflinger.so, then provide a logcat please. It may need hex edit (and I can do it).
4. Yes try it because sound need this lib.
I think first answer is the best... If the rom allow logcat access after replacement.
Edit 1: my Razr I is broken but I would like to help
Edit 2: Sound is very hard to works on porting rom (even if it's not the same thing with CM), so perhaps it needs some others files to change
Edit 3: Try to replace these libs too, with the chineze version:
/system/lib/libamc.so
/system/lib/libevent-listener.so
And you need to add FM's lib because ICS libaudioflinger.so needs these files:
Code:
12-05 16:14:35.939 527 527 E AudioHardwareALSA: Cannot load FM HW Module
http://xt890.blogspot.com.ar/2013/12/101-rom-cyanogenmod-build-3-para.html the site over there claims that the wifi is working..can you have a look?
EDIT: the rom download link is your google drive
Hazou said:
Unofficial CyanogenMod 10.1
Click to expand...
Click to collapse
Thanks!.. is a great news...
antkalaitzakis96 said:
http://xt890.blogspot.com.ar/2013/12/101-rom-cyanogenmod-build-3-para.html the site over there claims that the wifi is working..can you have a look?
EDIT: the rom download link is your google drive
Click to expand...
Click to collapse
Y' i know. He asked permission tot post it
Wifi working isn't a very big problem. I want to first hopefully fix the sound, or hope that some ideas might help.
Sent from my GT-P5110 using XDA Premium HD app
Hey can somebody post some screenshots ??
I don't think it's the right thread to post screenshot. This thread is for helping to develop and make all features work.
great .. thanks @Hazou
Enviado desde mi Moto usando Tapatalk
ICuaI said:
I don't think it's the right thread to post screenshot. This thread is for helping to develop and make all features work.
Click to expand...
Click to collapse
What would be the thread to post in, other than the one who actually presents the rom we are taking screenshots of?
hotpokets said:
What would be the thread to post in, other than the one who actually presents the rom we are taking screenshots of?
Click to expand...
Click to collapse
You don't need a screenshot, if this doesn't work yet. This is a thread to make the rom functional. Then it can be released to the regular users like us, who just want to use it regardless of the making process
You can go in every CM10.1-thread in this forum. I am sure that you will find enough screenshots of CM10.1. The rom for our xt890 doesn't have another look.
Or try this alpha-build on your own phone
And now for me I'll stop being of topic
Sorry for that to all the devs
GalaxyUser said:
Thanks for answer.
1. Try to replace libaudioflinger.so, then provide a logcat please. It may need hex edit (and I can do it).
4. Yes try it because sound need this lib.
I think first answer is the best... If the rom allow logcat access after replacement.
Edit 1: my Razr I is broken but I would like to help
Edit 2: Sound is very hard to works on porting rom (even if it's not the same thing with CM), so perhaps it needs some others files to change
Edit 3: Try to replace these libs too, with the chineze version:
/system/lib/libamc.so
/system/lib/libevent-listener.so
And you need to add FM's lib because ICS libaudioflinger.so needs these files:
Code:
12-05 16:14:35.939 527 527 E AudioHardwareALSA: Cannot load FM HW Module
Click to expand...
Click to collapse
So, i tested the methods u supposed.
first off, the roms doesn't need the fm module to work It's like the usb and hdmi audio modules that are expanding the audio functions, but aren't necessary for booting.
Than the rest, i found out that all the libamc, libevent*, libat-* etc. the files were we don't have the source from are the same as the stock jelly ones. So no need to change those. Like the other libs, mediaserver is the same as the one i compiled compared to the chinese 4.2.2 one.
For the libaudioflinger part, if i switch them, they won't boot up there service anymore. Why i doný know, but i have the feeling that the libaudioflinger won't solve the mystery.
Another thing i read from the logcat is that it crashes right at the moment the sound-card (medfieldaudio) aka 0x00000002 is called, after it is set that it can be used. So it seems to me that the alsa lib can't read the device properly. Somewhere allong the line a thing can't reach it or is giving the wrong data. But what....
The next thing i gonna try is making my own alsa module with tinyalsa implementation. To get only the sound working. FM and the audience driver won't work then. Great chance that it won't work, but you gotta try
Hazou said:
So, i tested the methods u supposed.
first off, the roms doesn't need the fm module to work It's like the usb and hdmi audio modules that are expanding the audio functions, but aren't necessary for booting.
Than the rest, i found out that all the libamc, libevent*, libat-* etc. the files were we don't have the source from are the same as the stock jelly ones. So no need to change those. Like the other libs, mediaserver is the same as the one i compiled compared to the chinese 4.2.2 one.
For the libaudioflinger part, if i switch them, they won't boot up there service anymore. Why i doný know, but i have the feeling that the libaudioflinger won't solve the mystery.
Another thing i read from the logcat is that it crashes right at the moment the sound-card (medfieldaudio) aka 0x00000002 is called, after it is set that it can be used. So it seems to me that the alsa lib can't read the device properly. Somewhere allong the line a thing can't reach it or is giving the wrong data. But what....
The next thing i gonna try is making my own alsa module with tinyalsa implementation. To get only the sound working. FM and the audience driver won't work then. Great chance that it won't work, but you gotta try
Click to expand...
Click to collapse
Will this ROM work on Lenovo K900?
charming.arpit said:
Will this ROM work on Lenovo K900?
Click to expand...
Click to collapse
Not out of the box, no.
Sent from my GT-P5110 using XDA Premium HD app
intel released source code for android 4.4
http://software.intel.com/en-us/articles/android-4-4-kitkat-x86-emulator-system-image
if its helpful
Did you guys saw this?
http://software.intel.com/en-us/articles/android-4-4-kitkat-x86-emulator-system-image
drunk_ryder24 said:
http://software.intel.com/en-us/articles/android-4-4-kitkat-x86-emulator-system-image
if its helpful
Click to expand...
Click to collapse
hey this is just
Android* 4.4 (KitKat) x86 Emulator System Image
this is for developers who running a pc (x86) and want to emulate the newest android.
this has nothing to do with our fone.
i think the problem is, this image dont got the drivers for our device.or any drivers expect for emulation.. dont know but thanks for the info that intel is developin
regard
28-05-2015
Hi all, i have update mu l90-d405n to lollipop 5.0.2, lg have complicated the infrared, i has thinking that they may put google native code to control infrared, no luck, google function consumerIRmanager return false, the 5.0.2 version cames with quicksetSDK version 1.73 they alter the way the service is implemented, had a hard time to test a way send the raw codes, the lg sample sdk does not work with quickset version 1.73.
To send raw codes with android 5.0.2 must be root, delete the directory /system/app/QuicksetSDK, then install QuicksetSDK version 1.69, reboot and the lg sample sdk works, use qremote to create a remote, then install my app and send raw ir works.
Sucess, its possible to send raw ir codes with L90.
Hi, i am trying to send a raw ir hex code from my phone, but until now no sucess.
The lg suport toll me that que hardware wasnt compatible with that, so i'm trying to find a solution.
Hipotese 1: use learn funtion of qremote sdk
Hipotese 2: use function send raw ir of qremote sdk
Hipotese 3: add a new raw ir code to the database of lg qremote
Hipotese 1, does not work
the learn function return false, the lg L90 does not have ir led receiver or the learn function is not implemented in kernel
Hipotese 2, does not work, the funtion return sucessfull but nothing is send by the ir, the funtion works on the g3, so maybe that function is not implemented in the kernel of L90
Hipotese 3, i have take a look inside the the app lgqremote and quicksetsdk but can find a database
Question: how or where is the qremote app from lg getting the codes to send to the ir ?
I have take a look at the qremote sdk and inside it, in the setup function it looks for the existence of quicksetsdk, so where is the qremote app getting the codes to send to ir ?
to be continue....................
Hi, tested the ConsumerIrManager API 19, the result was emiter not found, i test it in stock rom android 4.4.2, can any one with stock lollipop, maybe lg implemented that funtion in the new version.
to be continue............
Hi all, did a few more test, i copy the g3 qremote.apk and quicksetsdk.apk to L90, the infrared does not get detected, then try with the g2 version, the infrared get detected but qremote cant get the list of the remotes.
Can anyone with L90 d410 with stock lollipop put here the files:
- LGQremote.apk
- QuicksetSDK.apk
I like to test it to see what i can learn from it.
Can anyone anser the this question, does qremote lollipop version of L90 bring the same number os remote manufactures ?
Thanks.
Guys, check the LG G Pad 7 forum. They got the IR working on cm12 and maybe they can help with the IR on L90.
Edit:
The g pad 7 forum is inside the g pad 10.1 forum if you cannot find it. Maybe you can ask for help from invisiblek.
Sent from my LG-D415 using XDA Premium App
Thanks, going to see that.
hal_2000 said:
Hi all, did a few more test, i copy the g3 qremote.apk and quicksetsdk.apk to L90, the infrared does not get detected, then try with the g2 version, the infrared get detected but qremote cant get the list of the remotes.
Can anyone with L90 d410 with stock lollipop put here the files:
- LGQremote.apk
- QuicksetSDK.apk
I like to test it to see what i can learn from it.
Can anyone anser the this question, does qremote lollipop version of L90 bring the same number os remote manufactures ?
Thanks.
Click to expand...
Click to collapse
I can't find those files, there are however :
QuickRemote 4.40.14
Quickset SDK Lite 0.1.69
Hi gorankx, those are the files, i didnt put the version, those files are on stock lollipop of L90 ?
Can you put then here so i can make test it ?
Thanks.
Here it is
Hi gorankx, thanks for the files, going to test them.
One question, is lollipop on L90 fast ? and the batery last the same time ?
Hi, i have found the database file of qremote, is in /data/data/com.lge.qremote/databases/qremotesettings.db the db only has the info of the devices that you configure in a room of the qremote app, and it does not give the full info of the device, only gives device id, function id code, manufacture, it does not contain the data of the pulse and duration that is send to the infrared...... :crying:
On the other hand, there is a file devices.xml is not a realy a xml file, look like a binary file, that also gets update when we add a device in qremote app, that file is big, 30k to 40k in size is added to that file when we add a device, maybe that file contain the data pulse, the raw command codes
going to do more tests..........
To be continue................
hal_2000 said:
Hi gorankx, thanks for the files, going to test them.
One question, is lollipop on L90 fast ? and the batery last the same time ?
Click to expand...
Click to collapse
Good luck, LP is pretty good and battery life is also good but thats after hard reset, which i had to do
SUCESS, it works !!!
Hi, thanks to gorankx files it worked, the lgqremote.apk file is currupt it doesnt get recognize, but that doesnt matter because that is just a frontend with buttons, the real magic is on quicksetsdk.apk, that file has the info about the ir brands and codes, and its responsavel for the comunication with ir hardware, the lollipop version compare to kitkat has one more file "librctransport.so" , i think that lib is responsivel for sending raw codes.
When i tested the new quicksetsdk with qremote sdk it WORKED, we can now send raw ir codes from the L90, there is a small bug, with syncrony, dont know it is a problem with the lib, the file provably was compile for android 5 not 4.4, or if is bad implementation of sendirpattern function of qremote sdk, so the way i found to work must of the times is click 3 times on the power button of qremote apk and then click on raw ir button and the raw code gets transmited, i managed to turn on my tv (the lg app does not have my tv brand).
So thanks again to gorankx user, and lg for compile a new version quicksetsdk that works, it was ridiculous having a phone with infrared and dont be able to send ir raw codes.
Going to write a app to control my tv, this project is close successfully.
Thanks.
Is it possible to install on CM12 ROM? I am not able to install it...
hal_2000 said:
SUCESS, it works !!!
Hi, thanks to gorankx files it worked, the lgqremote.apk file is currupt it doesnt get recognize, but that doesnt matter because that is just a frontend with buttons, the real magic is on quicksetsdk.apk, that file has the info about the ir brands and codes, and its responsavel for the comunication with ir hardware, the lollipop version compare to kitkat has one more file "librctransport.so" , i think that lib is responsivel for sending raw codes.
When i tested the new quicksetsdk with qremote sdk it WORKED, we can now send raw ir codes from the L90, there is a small bug, with syncrony, dont know it is a problem with the lib, the file provably was compile for android 5 not 4.4, or if is bad implementation of sendirpattern function of qremote sdk, so the way i found to work must of the times is click 3 times on the power button of qremote apk and then click on raw ir button and the raw code gets transmited, i managed to turn on my tv (the lg app does not have my tv brand).
So thanks again to gorankx user, and lg for compile a new version quicksetsdk that works, it was ridiculous having a phone with infrared and dont be able to send ir raw codes.
Going to write a app to control my tv, this project is close successfully.
Thanks.
Click to expand...
Click to collapse
Will you develop and publish with us the app? My bedroom TV is a blaupunkt and the LG app doesn't have it either. Thanks in advance.
Sent from my LG-D405n using XDA Free mobile app
I'm glad i could help, could you explain us bit more, how that works, about raw codes?
Hi,
wizzardsk
it should be possible to install on cm12, must be root, quicksetsdk runs a service and i think it needs root to run it.
Disrupthorblaupunkt
I dont have a blaupunkt tv, you need the raw ir codes for that command.
i am thinking in making a very simple app, just to control my tv, but i can put a spinner that reads a file with raw codes in it, and then you add raw codes to that file and it should work with your tv, i havent start it yet, may take some time.
gorankx
Hi, thanks again, your file saved me a lot of work, i was trying to figure the format that lg puts in the device.xml so i could add more devices.
Your question, are you asking what is a ir raw code ?
R: infrared information is transmited in pulses, it based on a diod that is on/off, a raw code as information on frequency of transmition and duration of time of on state and off state, all remotes, all the keys function can be express with a raw code, one raw code for a key.
example lg power on, frequency = 38000 hz
// An example to send raw IR data, from qremote sdk
private void sendLgTvPower()
{
// test sendIRPattern()
int[] LGTVPower = {9000, 4500, 578, 552, 578, 552, 578, 1684, 578, 552, 578, 552, 578, 552,
578, 552, 578, 552, 578, 1684, 578, 1684, 578, 552, 578, 1684, 578, 1684, 578,
1684, 578, 1684, 578, 1684, 578, 552, 578, 552, 578, 552, 578, 1684, 578, 552, 578,
552, 578, 552, 578, 552, 578, 1684, 578, 1684, 578, 1684, 578, 552, 578, 1684, 578,
1684, 578, 1684, 578, 1684, 578, 39342, 9000, 2236, 578, 96184, 9000, 2236, 578,
96184};
mIR.sendIRPattern(38000, LGTVPower);
}
the numbers in the array represent the time in miliseconds that the diod in on, then off, then on.......etc
remote central has lots of raw ir codes for many devices, they are express in hex pronto codes, lg function need decimal numbers.
hope that helps.
So basically we can control any IR device by setting raw codes, btw where we can find raw codes, is there some kind web site or something like that with raw codes for different devices?
And i hope you can make app that makes process of adding new models easily. Well, wish you best!!!
hal_2000 said:
Hi,
wizzardsk
it should be possible to install on cm12, must be root, quicksetsdk runs a service and i think it needs root to run it.
Click to expand...
Click to collapse
Well, it does not work. I am root, of course, I installed quicksetsdk and I could not install the other app anyway (after installing: the app was not installed.)
Quick Remote for CISCO Set Top Box
How can I use LG L90 Quick Remote with CISCO z260 Set Top Box?
wizzardsk said:
Well, it does not work. I am root, of course, I installed quicksetsdk and I could not install the other app anyway (after installing: the app was not installed.)
Click to expand...
Click to collapse
Hi, quicksetsdk.apk installs a service to comunicate with ir hardware, it does not show anything to user, qremote.apk is a frontend with buttons, on that app when you click on a button it send a message to the service of quicksetsdk, and then the service sends the code to ir hardware.
On lg phone you need quicksetsdk to install the service, and qremote.apk or qremote sdk sample to be the frontend to be able to work with ir.
Hi guys,
I resently installed CM12.1-20151117 on my Moto X XT1052.
The reason I installed CM is that I got the "couldn't connect to camera" bug a lot. Unfortunately the bug is still there. I tried the restart camera apk with the cm camera fix app, renaming the DCIM folder, clearing the app data (camera and gallery) and multiple reboots as well as any combination of these fixes.
Sometimes one of the above solutions will work, but most of the time I end up with only the front camera working.
Does anyone have a working solution for this very annoying bug?
Thank you in advance!
Gesendet von meinem SHIELD Tablet mit Tapatalk
braumeisteresche said:
Hi guys,
I resently installed CM12.1-20151117 on my Moto X XT1052.
The reason I installed CM is that I got the "couldn't connect to camera" bug a lot. Unfortunately the bug is still there. I tried the restart camera apk with the cm camera fix app, renaming the DCIM folder, clearing the app data (camera and gallery) and multiple reboots as well as any combination of these fixes.
Sometimes one of the above solutions will work, but most of the time I end up with only the front camera working.
Does anyone have a working solution for this very annoying bug?
Thank you in advance!
Gesendet von meinem SHIELD Tablet mit Tapatalk
Click to expand...
Click to collapse
Is kernel samepage merging enabled? If yes use kernel aduitor and disable it, check apply at start and reboot. Report back if this helps.
Sent from my K007 using XDA Free mobile app
tycoo said:
Is kernel samepage merging enabled? If yes use kernel aduitor and disable it, check apply at start and reboot. Report back if this helps.
Sent from my K007 using XDA Free mobile app
Click to expand...
Click to collapse
Well, I googled samepage merging, but couldn't find it.
Were can I find this option?
Thanks!
Gesendet von meinem SHIELD Tablet mit Tapatalk
braumeisteresche said:
Well, I googled samepage merging, but couldn't find it.
Were can I find this option?
Thanks!
Gesendet von meinem SHIELD Tablet mit Tapatalk
Click to expand...
Click to collapse
Sorry, forget about that. I cm12.1 ksm is not enabled by default anyway. Best would be to change to this thread here: http://forum.xda-developers.com/moto-x/development/rom-cyanogenmod-12-moto-x-t2995381/post64492139 , follow the instructions to get a log and post it.
tycoo said:
Sorry, forget about that. I cm12.1 ksm is not enabled by default anyway. Best would be to change to this thread here: http://forum.xda-developers.com/moto-x/development/rom-cyanogenmod-12-moto-x-t2995381/post64492139 , follow the instructions to get a log and post it.
Click to expand...
Click to collapse
Hi again,
I managed to get a log file: http://d-h.st/yEfW
Thanks a lot!
braumeisteresche said:
Hi again,
I managed to get a log file: http://d-h.st/yEfW
Thanks a lot!
Click to expand...
Click to collapse
Puh, yes there is a bug but i can not see what is the cause or how to interpret it too.
Can you just connect you phone via adb, start logging, start the camera and let it crash, stop logging and post the log file again.
EDIT: Look here for instructions http://forum.xda-developers.com/showthread.php?t=1726238 or here https://wiki.cyanogenmod.org/w/Doc:_debugging_with_logcat/de
type "adb devices" before to check if you device is recognized
There is another assumption. I never get harmed by, but i have read somewhere that cm12.1 needs the latest motorola firmware to work properly, otherwise you get some other errors, like a none working phone speaker. Therefore, did you update your phone to the latest stock lollipop rom before, or did you switch from any kitkat rom? If it is the latter there is a method to flash the latest firmware files manually.
But i never did this because i didnt need that. If you search around in the other threads you will find the correct instructions. Be carefull! If you flash the wrong files you can brick your phone, so be sure you grabbed the correct firmware for your phone model.
Hi,
I had stock 5.1 running and changed to CM 12.1 in the hope this would solve the camera issue.
Getting the camera to crash seems not to work atm.
Will post the log file as soon as I manage to get the camera to crash.
Allright,
btw i am using the moto camera from this thread and can recommend it:
http://forum.xda-developers.com/moto-g/themes-apps/app-moto-camera-exposure-control-gallery-t3124309
There are some more camera versions in the moto g apps and themes forum which will work too i guess
another log
Hi,
Finally I managed to get a log file with the camera app crashing.
http://d-h.st/RuH4
I switched to the moto cam as well (the one you posted).
The moto cam is just the best
thanks
braumeisteresche said:
Hi,
Finally I managed to get a log file with the camera app crashing.
http://d-h.st/RuH4
I switched to the moto cam as well (the one you posted).
The moto cam is just the best
thanks
Click to expand...
Click to collapse
Isn't it the same log you posted before already? There is nowhere an entry with "Start proc ...camera...bla bla"
Seems like I made a mistake along the way.
Now I did:
- "adb logcat -c"
- "logcat -d -f /sdcard/logcat.log *:V"
- "adb pull /sdcard/logcard.log"
The file now contains "camera" quite a bit (I started the camera twice and it crashed both times).
http://d-h.st/IXRQ
Thanks.
braumeisteresche said:
Seems like I made a mistake along the way.
Now I did:
- "adb logcat -c"
- "logcat -d -f /sdcard/logcat.log *:V"
- "adb pull /sdcard/logcard.log"
The file now contains "camera" quite a bit (I started the camera twice and it crashed both times).
http://d-h.st/IXRQ
Thanks.
Click to expand...
Click to collapse
Sorry for the late reply.
Yep, thats a good log.
Essentially these are the relevant lines (5769-5815):
Code:
E/mm-camera-intf( 268): mm_camera_open: opened, break out while loop
E/mm-camera-intf( 268): mm_camera_open: cannot open control fd of '/dev/video0' (Device or resource busy)
E/mm-camera-intf( 268): camera_open: mm_camera_open err = -1
E/QCameraHWI( 268): startCamera: cam_ops_open failed: id = 0
E/QCameraHWI( 268): mCamera handle or state is invalid mCameraHandle=0x0,camera state=0
E/QualcommCamera( 268): int android::camera_device_open(const hw_module_t*, const char*, hw_device_t**): end rc -1
I/CameraHalWatchdog( 268): Stopped Watchdog Thread...
E/CameraWrapper( 268): vendor camera open fail
E/CameraClient( 268): Could not open camera 0: -19
E/CameraClient( 268): initialize: Camera 0: unable to initialize device: No such device (-19)
I/CameraClient( 268): Destroying camera 0
E/CameraService( 268): connectFinishUnsafe: Could not initialize client from HAL module.
W/AudioFlinger( 268): session id 773 not found for pid 25210
W/AudioFlinger( 268): session id 774 not found for pid 25210
W/CameraBase(25210): An error occurred while connecting to camera: 0
W/ServiceManager( 268): Permission failure: android.permission.DUMP from uid=10091 pid=25550
W/OpenCameraCallable(25210): Exception in result (dur:212)
W/OpenCameraCallable(25210): com.motorola.camera.device.execption.CameraHardwareException: java.lang.RuntimeException: Fail to connect to camera service
W/OpenCameraCallable(25210): at com.motorola.camera.device.callables.OpenCameraCallable.openCamera(OpenCameraCallable.java:133)
W/OpenCameraCallable(25210): at com.motorola.camera.device.callables.OpenCameraCallable.call(OpenCameraCallable.java:62)
W/OpenCameraCallable(25210): at com.motorola.camera.device.callables.CameraCallable.run(CameraCallable.java:47)
W/OpenCameraCallable(25210): at com.motorola.camera.device.CameraService$2.handleMessage(CameraService.java:108)
W/OpenCameraCallable(25210): at android.os.Handler.dispatchMessage(Handler.java:98)
W/OpenCameraCallable(25210): at android.os.Looper.loop(Looper.java:135)
W/OpenCameraCallable(25210): at android.os.HandlerThread.run(HandlerThread.java:61)
W/OpenCameraCallable(25210): Caused by: java.lang.RuntimeException: Fail to connect to camera service
W/OpenCameraCallable(25210): at android.hardware.Camera.<init>(Camera.java:529)
W/OpenCameraCallable(25210): at android.hardware.Camera.open(Camera.java:364)
W/OpenCameraCallable(25210): at com.motorola.camera.device.callables.OpenCameraCallable.openCamera(OpenCameraCallable.java:169)
W/OpenCameraCallable(25210): at com.motorola.camera.device.callables.OpenCameraCallable.openCamera(OpenCameraCallable.java:112)
W/OpenCameraCallable(25210): ... 6 more
W/ReadParamsCallable(25210): Exception in result (dur:1)
W/ReadParamsCallable(25210): java.lang.Exception: Camera isn't opened
W/ReadParamsCallable(25210): at com.motorola.camera.device.callables.ReadParamsCallable.call(ReadParamsCallable.java:29)
W/ReadParamsCallable(25210): at com.motorola.camera.device.callables.CameraCallable.run(CameraCallable.java:47)
W/ReadParamsCallable(25210): at com.motorola.camera.device.CameraService$2.handleMessage(CameraService.java:108)
W/ReadParamsCallable(25210): at android.os.Handler.dispatchMessage(Handler.java:98)
W/ReadParamsCallable(25210): at android.os.Looper.loop(Looper.java:135)
W/ReadParamsCallable(25210): at android.os.HandlerThread.run(HandlerThread.java:61)
W/SetParamsCallable(25210): Exception in result (dur:2)
W/SetParamsCallable(25210): java.lang.Exception: Camera isn't opened
W/SetParamsCallable(25210): at com.motorola.camera.device.callables.SetParamsCallable.call(SetParamsCallable.java:58)
W/SetParamsCallable(25210): at com.motorola.camera.device.callables.CameraCallable.run(CameraCallable.java:47)
W/SetParamsCallable(25210): at com.motorola.camera.device.CameraService$2.handleMessage(CameraService.java:108)
W/SetParamsCallable(25210): at android.os.Handler.dispatchMessage(Handler.java:98)
W/SetParamsCallable(25210): at android.os.Looper.loop(Looper.java:135)
W/SetParamsCallable(25210): at android.os.HandlerThread.run(HandlerThread.java:61)
Unfortunately now comes the hard part to understand the output.
Two thoughts. First, maybe it is worth to test the kernel i published in the android development section. I am not sure if it will fix the problem, though i merged some camera updates in there.
Second, as you had this problem with the stock rom too, in the worst case it may be a hardware error.
Btw, did you google and search around if this problem is maybe a common one and occured on other phones and roms too?
Hi,
Thanks for your reply!
I will look for that kernel of yours and will try it later today.
The issue seems to be a bug according to google.
It appears on various phones (nexus, Samsung, etc.).
Some fixes are available as well (I tried them all).
Cheers
Gesendet von meinem SHIELD Tablet mit Tapatalk
Hi,
I finally installed your kernel. Also I had to fix the GPS as well (deleted modemst1+2).
The camera worked for 2 minutes then wouldn't start anymore.
Maybe it is a hardware defect after all. Too bad
Looking for a good replacements at the moment - one plus two might be an option...
Thank you for your help!
Gesendet von meinem Moto X mit Tapatalk
braumeisteresche said:
Hi,
I finally installed your kernel. Also I had to fix the GPS as well (deleted modemst1+2).
The camera worked for 2 minutes then wouldn't start anymore.
Maybe it is a hardware defect after all. Too bad
Looking for a good replacements at the moment - one plus two might be an option...
Thank you for your help!
Gesendet von meinem Moto X mit Tapatalk
Click to expand...
Click to collapse
Tja, das ist Mist. Weitere Ideen habe ich im Moment auch nicht. Sorry