Database Develop

[Discussion]Building CM10 for p990

To keep my Threat "[GUIDE] Bulding CM9 from Sources for O2X (P990)" clean, I decided to open a new Threat in General Section,
lets use this Threat to discuss about compiling CM10 for the O2X.

thorstenhirsch said:
1. Changed "default revision" in manifest.xml to jellybean.
Code:
manifest.xml: <default revision="refs/heads/jellybean"
Click to expand...
Click to collapse
You have to download the jellybean sourcecode,
possibly it`s better to init the sources to a different folder e.g. /CM10/android/system
if you want to keep the CM9 sources, too.
Code:
cd ~/CM10/android/system/
Code:
repo init -u git://github.com/CyanogenMod/android.git -b jellybean
you have to create all files for yellybean which are added to local_manifest.xml, or find jellybean branches for those files on github, (I don`t know if there are jellybean branches for our O2X, I didn`t searched for it)

When removing all entries from local_manifest.xml "repo sync" works at least. But well... I think now I've got the same as I had after "repo init [...] -b jellybean". So I still need jellybean-ed repos for /system/device/lge/star-common and p990. Guess I start with the CM9 versions...

That`s exactly what I mean,
without the necessary working jellybean files, it makes no sense to try building CM10 for O2X,
except you are able to create the necessary working jellybean files by yourself,

Stuck with this:
Code:
device/lge/star-common/include/media/MediaPlayerInterface.h:165:25: note: virtual void android::MediaPlayerBase::sendEvent(int, int, int)
device/lge/star-common/include/media/MediaPlayerInterface.h:165:25: note: candidate expects 3 arguments, 4 provided
This is the code line:
Code:
158 virtual status_t getMetadata(const media::Metadata::Filter& ids,
159 Parcel *records) {
160 return INVALID_OPERATION;
161 };
162
163 virtual status_t setLGAudioEffect(int ) { return NO_ERROR; };
164
165 virtual void sendEvent(int msg, int ext1=0, int ext2=0) { if (mNotify) mNotify(mCookie, msg, ext1, ext2); }
Any ideas of how to avoid this?

Hey.
Without some serious modifications or to be more precisely hacks. Like the one introduced in cm9 and more. Like disabling and hacking around the project butter features. Like dealing with the vsync etc.
Anyway. Without these features a cm10 build doesn't make sense at all. Just more hacks and instabilities. It won't run better than the cm9 builds and the biggest improvement is the smoothness. The other stuff isn't worth the update. Without a OEM update to ICS a jb build isn't worth the amount of work. Not even the compile time. Sorry to say that. (And yeah I looked into it and had some progress. However it's not worth the time.)
Sent from my Nexus S using xda app-developers app

Benee said:
Hey.
Without some serious modifications or to be more precisely hacks. Like the one introduced in cm9 and more. Like disabling and hacking around the project butter features. Like dealing with the vsync etc.
Anyway. Without these features a cm10 build doesn't make sense at all. Just more hacks and instabilities. It won't run better than the cm9 builds and the biggest improvement is the smoothness. The other stuff isn't worth the update. Without a OEM update to ICS a jb build isn't worth the amount of work. Not even the compile time. Sorry to say that. (And yeah I looked into it and had some progress. However it's not worth the time.)
Sent from my Nexus S using xda app-developers app
Click to expand...
Click to collapse
Yeah, i think all we know that. But i'm trying to make it with educational purpouses. I don't want to make a ROM with graphic acceleration and the other stuff that didn't work in cm9, cause it's impossible.
The only one thing i'mt trying is to bake some from sources and make it run on my phone. And maybe make a start point to make my roms for personal use.
If anyone want to help, i would be greatfull. If you don't want to help, it's ok. Probably you have better things to do xD.
Cya

ethansp said:
Stuck with this:
Code:
device/lge/star-common/include/media/MediaPlayerInterface.h:165:25: note: virtual void android::MediaPlayerBase::sendEvent(int, int, int)
device/lge/star-common/include/media/MediaPlayerInterface.h:165:25: note: candidate expects 3 arguments, 4 provided
This is the code line:
Code:
158 virtual status_t getMetadata(const media::Metadata::Filter& ids,
159 Parcel *records) {
160 return INVALID_OPERATION;
161 };
162
163 virtual status_t setLGAudioEffect(int ) { return NO_ERROR; };
164
165 virtual void sendEvent(int msg, int ext1=0, int ext2=0) { if (mNotify) mNotify(mCookie, msg, ext1, ext2); }
Any ideas of how to avoid this?
Click to expand...
Click to collapse
You need to update this file to JB. It's currently based on the ICS MediaPlayerInterface.h and then you need some audio hacks (the shim by arcee).
With the above I was talking about: Without these hacks the build will run worser than a sdk port. Unusable worse. Even with dev spirit it was just a temp flash.

Benee said:
You need to update this file to JB. It's currently based on the ICS MediaPlayerInterface.h and then you need some audio hacks (the shim by arcee).
With the above I was talking about: Without these hacks the build will run worser than a sdk port. Unusable worse. Even with dev spirit it was just a temp flash.
Click to expand...
Click to collapse
Yes, probably you have all the reason about this. But, if i can taking some advantages in the developing of a "experimental" build waiting for some sources from nvidia/LGE an then implement it. I think the work is not going all to trash. Maybe in the future, can we use it, probably not. Ok. But if people want, what is the inconvenience of "loosing" time trying to make it work?
Cya.

Ok, i've do some advances, now logcat is running but stuck on 2nd lg boot logo.
If want to know the changes i have make: https://github.com/ethansp
And the logcat: http://pastebin.com/SZGwM0Xm
The errors i've seen:
Code:
E/libEGL ( 1175): eglGetDisplay:121 error 300c (EGL_BAD_PARAMETER)
E/libEGL ( 1175): eglInitialize:137 error 3008 (EGL_BAD_DISPLAY)
E/libEGL ( 1175): validate_display:209 error 3008 (EGL_BAD_DISPLAY)
E/libEGL ( 1175): validate_display:209 error 3008 (EGL_BAD_DISPLAY)
F/libc ( 1175): Fatal signal 11 (SIGSEGV) at 0xdeadbaad (code=1), thread 1192 (SurfaceFlinger)
Code:
D/dalvikvm( 1176): DexOpt: incorrect opt magic number (0xff ff ff ff)
D/dalvikvm( 1176): ODEX file is stale or bad; removing and retrying (/data/dalvik-cache/[email protected]@[email protected])
Code:
I/ServiceManager( 1008): service 'media.audio_flinger' died
I/ServiceManager( 1008): service 'media.player' died
I/ServiceManager( 1008): service 'media.camera' died
I/ServiceManager( 1008): service 'media.audio_policy' died

Just a few ideas...
Regarding the EGL errors: probably some of the proprietary vendor files are missing (check /bin, /etc, /lib) or not included correctly.
The audio errors are most likely the result of the changes Google made to the audio system of JB. If these errors are critical to booting try compiling the rom without audio.
Good luck and keep on trying!
Have a nice day!

ethansp said:
Ok, i've do some advances, now logcat is running but stuck on 2nd lg boot logo.
If want to know the changes i have make: https://github.com/ethansp
And the logcat: http://pastebin.com/SZGwM0Xm
The errors i've seen:
Code:
E/libEGL ( 1175): eglGetDisplay:121 error 300c (EGL_BAD_PARAMETER)
E/libEGL ( 1175): eglInitialize:137 error 3008 (EGL_BAD_DISPLAY)
E/libEGL ( 1175): validate_display:209 error 3008 (EGL_BAD_DISPLAY)
E/libEGL ( 1175): validate_display:209 error 3008 (EGL_BAD_DISPLAY)
F/libc ( 1175): Fatal signal 11 (SIGSEGV) at 0xdeadbaad (code=1), thread 1192 (SurfaceFlinger)
Click to expand...
Click to collapse
EGL issues are related to the missing egl hacks from arcee (here for ics) (I think you need add even more hacks than in ics due to vsync etc.).
ethansp said:
Code:
D/dalvikvm( 1176): DexOpt: incorrect opt magic number (0xff ff ff ff)
D/dalvikvm( 1176): ODEX file is stale or bad; removing and retrying (/data/dalvik-cache/[email protected]@[email protected])
Click to expand...
Click to collapse
This error is related to above error.
ethansp said:
Code:
I/ServiceManager( 1008): service 'media.audio_flinger' died
I/ServiceManager( 1008): service 'media.player' died
I/ServiceManager( 1008): service 'media.camera' died
I/ServiceManager( 1008): service 'media.audio_policy' died
Click to expand...
Click to collapse
Same as above. Your complete egl driver etc is going down.
Raum1807 said:
Just a few ideas...
Regarding the EGL errors: probably some of the proprietary vendor files are missing (check /bin, /etc, /lib) or not included correctly.
The audio errors are most likely the result of the changes Google made to the audio system of JB. If these errors are critical to booting try compiling the rom without audio.
Good luck and keep on trying!
Have a nice day!
Click to expand...
Click to collapse
Getting audio running shouldn't be too difficult. You basically need to add the ics audio shim and make some adjustment to eventual JB changes. It will most likely bug around without working audio (mediaserver is crashing)
EDIT:
Ok. Had a closer look. In CM nearly everything is implemented. Like this for audio and this for egl etc. You just need to update the cam lib, the audio includes and it should boot and work partly.

Benee said:
EGL issues are related to the missing egl hacks from arcee (here for ics) (I think you need add even more hacks than in ics due to vsync etc.).
This error is related to above error.
Same as above. Your complete egl driver etc is going down.
Getting audio running shouldn't be too difficult. You basically need to add the ics audio shim and make some adjustment to eventual JB changes. It will most likely bug around without working audio (mediaserver is crashing)
EDIT:
Ok. Had a closer look. In CM nearly everything is implemented. Like this for audio and this for egl etc. You just need to update the cam lib, the audio includes and it should boot and work partly.
Click to expand...
Click to collapse
Lot of thanks benee for taking some time to watch it.
I have moded the expresions about the storages (changed /mnt/sdcard to /storage/scdcard0 ) and moded de libslights.c in the frameworks. a new logcat and seems very improved. Stays the screen black cause not working properly de egl driver. I'm going to take a look. I think there is a problem with kernel>drivers expresions.
Latest logcat if you want to take a look: http://pastebin.com/L3hjvTEi

ethansp said:
Lot of thanks benee for taking some time to watch it.
I have moded the expresions about the storages (changed /mnt/sdcard to /storage/scdcard0 ) and moded de libslights.c in the frameworks. a new logcat and seems very improved. Stays the screen black cause not working properly de egl driver. I'm going to take a look. I think there is a problem with kernel>drivers expresions.
Latest logcat if you want to take a look: http://pastebin.com/L3hjvTEi
Click to expand...
Click to collapse
I've send you some pull requests. Due to lag of time I havn't compiled them. Hope you can fire up a compile and send me a log and report if you noticed a improvement.

Benee said:
I've send you some pull requests. Due to lag of time I havn't compiled them. Hope you can fire up a compile and send me a log and report if you noticed a improvement.
Click to expand...
Click to collapse
A lot of thanks. i've see it. Doing the compile now. When finish i will post the results.

Hi, no solution. Stills blackscreen, same EGL errors, and i discovered, logcat only work on first boot. if i pull battery off and on, no more logcat until wipes.
I let here the logcat: http://pastebin.com/TH1wCsvV
Thanks for help.

ethansp said:
Hi, no solution. Stills blackscreen, same EGL errors, and i discovered, logcat only work on first boot. if i pull battery off and on, no more logcat until wipes.
I let here the logcat: http://pastebin.com/TH1wCsvV
Thanks for help.
Click to expand...
Click to collapse
Oh sure.. Yeah wait a moment . We need some more ported over changes.
EDIT:
use this this and that instead of the cm ones or cherry-pick the changes.
EDIT2:
Doing some blind RIL changes. Maybe they're working out - currently my girlfriend uses my o2x because her phone got stolen.
EDIT3:
and add frameworks_base. If the phone boots, please send me a adb logcat -b radio. I need the logcat from booting till 30 secs booted up rom. I suggest routing it to a txt file because the log is quite spammy.
EDIT4:
I created a repo for easier syncing: here

Benee said:
Oh sure.. Yeah wait a moment . We need some more ported over changes.
EDIT:
use this this and that instead of the cm ones or cherry-pick the changes.
EDIT2:
Doing some blind RIL changes. Maybe they're working out - currently my girlfriend uses my o2x because her phone got stolen.
EDIT3:
and add frameworks_base. If the phone boots, please send me a adb logcat -b radio. I need the logcat from booting till 30 secs booted up rom. I suggest routing it to a txt file because the log is quite spammy.
Click to expand...
Click to collapse
Ok. I'm at work right now, in 5 hours i go home. Expect results in ~7 hours or tomorrow in morning.
Thanks a lot for all your help.

you're the man benee

Benee said:
Oh sure.. Yeah wait a moment . We need some more ported over changes.
EDIT:
use this this and that instead of the cm ones or cherry-pick the changes.
EDIT2:
Doing some blind RIL changes. Maybe they're working out - currently my girlfriend uses my o2x because her phone got stolen.
EDIT3:
and add frameworks_base. If the phone boots, please send me a adb logcat -b radio. I need the logcat from booting till 30 secs booted up rom. I suggest routing it to a txt file because the log is quite spammy.
EDIT4:
I created a repo for easier syncing: here
Click to expand...
Click to collapse
Ok, phone boots, but the radio logcat only output this:
Code:
D/RILD ( 1011): radio disabled
D/RILB ( 1268): /proc/[email protected] [email protected] loglevel=0 muic_state=1 lpj=9994240 CRC=3010002a8e458d7 vmalloc=256M brdrev=1.0 video=tegrafb console=ttyS0,115200n8 usbcore.old_scheme_first=1 tegraboot=sdmmc tegrapart=recovery:35e00:2800:800,linux:34700:1000:800,mbr:400:200:800,system:600:2bc00:800,cache:2c200:8000:800,misc:34200:400:800,userdata:38700:c0000:800 androidboot.hardware=p990
D/RILB ( 1268): getLteOnCdmaMode=0 curVal=-1 product_type='' lteOnCdmaProductType=''
I have to say, i didn't understand the "edit 3" add frameworks base, where? I have synced it but have to take out from star.mk cause that files now exist only in frameworks/native.
Edit: forgot to say: FC's com.android.phone repeteavly. Tonyp, how did you that? xD
Edit2: Latest logcat without -b radio trigger: http://pastebin.com/ASUyM0vR
When load this service "884.I/SystemServer( 1270): AssetRedirectionManager Service" (you can find it at end of logcat) the logcat stops, is like usb get disabled. If i reboot, no more logcat output until full wipes.
Edit3: took off phone.apk and FC's media, and voice syntethizer.

Camera Problem With CM10.1 AND LiquidSmooth S3 i9305 (with the latest versions)

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 ?

Xposed 2.7 experimental version feedback

I have just uploaded a test version of Xposed Installer.
It doesn't have anything to do with ART!!!
In fact, there is no change in the framework itself, only in the installer. I would just like to get some early testing of a bigger change.
The test version uses a database to manage the list of downloadable modules. Previously, all the modules were loaded from an XML file on every start and kept in the memory. That worked fine, but with more and more modules in the repository, I had to rethink.
Some advantages of the new approach are:
- The XML doesn't need to be parsed on every start. Instead, the previously parsed state is available immediately.
- Reloading the repository index from the server can be done incrementally, loading only those modules which have changed since the last refresh. This significantly reduces traffic for both you and me. The full index has grown to about 350 kB (gzipped, it's ~1.6 MB uncompressed). The incremental updates are just a fraction of that. These XMLs are also much faster to parse than the big ones.
- Probably less memory usage, because only the currently used data needs to be kept in the memory. Information about all the other available modules can be loaded from the database when required.
- More flexibility in the future, e.g. for enhanced search. I have no plans at the moment and many other things are more important, but SQL allows for interesting queries without too much code.
If you're already using Xposed and want to help checking for bugs, feel free to download the test version. Assuming you are using version 2.6/.1, just open click on "Xposed Installer", then swipe twice to go to the module-specific settings. Select "Experimental" and the new version should show up. If not, press the refresh button once.
Please report here if you noticed any UI issues which are potentionally related to the introduction of the database. For crashes, please post a logcat showing the error. Thanks a lot for testing!
Please don't report installation or framework issues here. If you haven't used Xposed before, you should install the stable version 2.6.1 instead.

andreasf93 said:
It's close
http://www.androidauthority.com/art-replaces-dalvik-aosp-394904/
Click to expand...
Click to collapse
I would laugh about your joke if people weren't constantly bringing up ART ever since Google has presented it... which is really demotivating.

Not ART related should be bigger and red ^^
At updating to 2.7 i got a FC, not sure if this log helps
Code:
06-19 17:42:51.084: I/WindowState(1654): WIN DEATH: Window{4210d278 u0 de.robv.android.xposed.installer/de.robv.android.xposed.installer.WelcomeActivity}
06-19 17:42:51.092: I/ActivityManager(1654): Process de.robv.android.xposed.installer (pid 8415) has died.
06-19 17:42:51.092: W/ActivityManager(1654): Force removing ActivityRecord{41fdcc40 u0 de.robv.android.xposed.installer/.XposedInstallerActivity t318}: app died, no saved state
06-19 17:42:51.115: I/WindowState(1654): WIN DEATH: Window{421328b0 u0 de.robv.android.xposed.installer/de.robv.android.xposed.installer.XposedInstallerActivity}
06-19 17:42:51.241: I/ActivityManager(1654): Displayed com.android.packageinstaller/.PackageInstallerActivity: +2s554ms
06-19 17:42:51.241: I/Timeline(1654): Timeline: Activity_windows_visible id: ActivityRecord{4202b4a8 u0 com.android.packageinstaller/.PackageInstallerActivity t319} time:92810640
06-19 17:42:51.248: W/InputMethodManagerService(1654): Got RemoteException sending setActive(false) notification to pid 8415 uid 10061
06-19 17:42:51.272: W/Binder(1934): Caught a RuntimeException from the binder stub implementation.
06-19 17:42:51.272: W/Binder(1934): java.lang.NullPointerException
06-19 17:42:51.272: W/Binder(1934): at android.inputmethodservice.IInputMethodWrapper.setSessionEnabled(IInputMethodWrapper.java:280)
06-19 17:42:51.272: W/Binder(1934): at com.android.internal.view.IInputMethod$Stub.onTransact(IInputMethod.java:129)
06-19 17:42:51.272: W/Binder(1934): at android.os.Binder.execTransact(Binder.java:404)
06-19 17:42:51.272: W/Binder(1934): at dalvik.system.NativeStart.run(Native Method)
06-19 17:42:51.404: I/Timeline(8474): Timeline: Activity_idle id: [email protected] time:92810797
After a restart of the app i cant install it because of "Das Paket ist offenbar beschädigt"
in the error.log i have multiple times this message. The app is installed and is not an xposed module
Code:
java.lang.IllegalStateException: Unable to get package info for de.defim.apk.XXX; is package not installed?
at android.app.LoadedApk.initializeJavaContextClassLoader(LoadedApk.java:371)
at android.app.LoadedApk.getClassLoader(LoadedApk.java:324)
at de.robv.android.xposed.XposedBridge$1.beforeHookedMethod(XposedBridge.java:205)
at de.robv.android.xposed.XposedBridge.handleHookedMethod(XposedBridge.java:611)
at android.app.ActivityThread.handleBindApplication(Native Method)
at android.app.ActivityThread.access$1500(ActivityThread.java:145)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1266)
at android.os.Handler.dispatchMessage(Handler.java:102)
at android.os.Looper.loop(Looper.java:136)
at android.app.ActivityThread.main(ActivityThread.java:5161)
at java.lang.reflect.Method.invokeNative(Native Method)
at java.lang.reflect.Method.invoke(Method.java:515)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:795)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:611)
at de.robv.android.xposed.XposedBridge.main(XposedBridge.java:132)
at dalvik.system.NativeStart.main(Native Method)
What do you think about to add the date+time to the xposed-log?

defim said:
Not ART related should be bigger and red ^^
At updating to 2.7 i got a FC, not sure if this log helps
Click to expand...
Click to collapse
I made the text red now...
Regarding the FC, unfortunately it starts directly after the error, but doesn't show the error itself.

rovo89 said:
I made the text red now...
Regarding the FC, unfortunately it starts directly after the error, but doesn't show the error itself.
Click to expand...
Click to collapse
I found more lines ...
Code:
06-19 17:42:45.701: W/dalvikvm(8415): threadid=16: thread exiting with uncaught exception (group=0x415a3ce0)
06-19 17:42:45.709: E/AndroidRuntime(8415): FATAL EXCEPTION: DownloadMonitor
06-19 17:42:45.709: E/AndroidRuntime(8415): Process: de.robv.android.xposed.installer, PID: 8415
06-19 17:42:45.709: E/AndroidRuntime(8415): java.lang.NullPointerException
06-19 17:42:45.709: E/AndroidRuntime(8415): at de.robv.android.xposed.installer.widget.DownloadView$DownloadMonitor.run(DownloadView.java:193)
06-19 17:42:45.717: W/ActivityManager(1654): Force finishing activity de.robv.android.xposed.installer/.DownloadDetailsActivity
06-19 17:42:45.998: W/ResourceType(1654): Skipping entry 0x7f040000 in package table 0 because it is not complex!
06-19 17:42:46.014: W/ResourceType(1654): Skipping entry 0x7f040003 in package table 0 because it is not complex!
I extended my above post with lines of error.log, dont miss it

Good job :good: updates really quick

in the error.log i have multiple times this message. The app is installed and is not an xposed module
Code:
java.lang.IllegalStateException: Unable to get package info for de.defim.apk.XXX; is package not installed?
at android.app.LoadedApk.initializeJavaContextClassLoader(LoadedApk.java:371)
at android.app.LoadedApk.getClassLoader(LoadedApk.java:324)
at de.robv.android.xposed.XposedBridge$1.beforeHookedMethod(XposedBridge.java:205)
at de.robv.android.xposed.XposedBridge.handleHookedMethod(XposedBridge.java:611)
at android.app.ActivityThread.handleBindApplication(Native Method)
at android.app.ActivityThread.access$1500(ActivityThread.java:145)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1266)
at android.os.Handler.dispatchMessage(Handler.java:102)
at android.os.Looper.loop(Looper.java:136)
at android.app.ActivityThread.main(ActivityThread.java:5161)
at java.lang.reflect.Method.invokeNative(Native Method)
at java.lang.reflect.Method.invoke(Method.java:515)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:795)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:611)
at de.robv.android.xposed.XposedBridge.main(XposedBridge.java:132)
at dalvik.system.NativeStart.main(Native Method)
Click to expand...
Click to collapse
That looks more like an issue with the package manager than with Xposed. Kind of fits to your description that it says that the other package is not installed.
What do you think about to add the date+time to the xposed-log?
Click to expand...
Click to collapse
I don't think it's necessary.
defim said:
I found more lines ...
Code:
06-19 17:42:45.701: W/dalvikvm(8415): threadid=16: thread exiting with uncaught exception (group=0x415a3ce0)
06-19 17:42:45.709: E/AndroidRuntime(8415): FATAL EXCEPTION: DownloadMonitor
06-19 17:42:45.709: E/AndroidRuntime(8415): Process: de.robv.android.xposed.installer, PID: 8415
06-19 17:42:45.709: E/AndroidRuntime(8415): java.lang.NullPointerException
06-19 17:42:45.709: E/AndroidRuntime(8415): at de.robv.android.xposed.installer.widget.DownloadView$DownloadMonitor.run(DownloadView.java:193)
06-19 17:42:45.717: W/ActivityManager(1654): Force finishing activity de.robv.android.xposed.installer/.DownloadDetailsActivity
06-19 17:42:45.998: W/ResourceType(1654): Skipping entry 0x7f040000 in package table 0 because it is not complex!
06-19 17:42:46.014: W/ResourceType(1654): Skipping entry 0x7f040003 in package table 0 because it is not complex!
I extended my above post with lines of error.log, dont miss it
Click to expand...
Click to collapse
Ok, that's a known error: https://github.com/rovo89/XposedInstaller/issues/182
But except for crashing Xposed Installer, nothing can happen. Looking at the error you posted above, I assume your system is in an inconstistent state.

In which way inconsistent? Today I was developing with the app causing the IllegalStateException, so it's a debug version. But it is installed and running properly. Maybe some things of it changed since Xposed installer started the 1st time
rovo89 said:
But except for crashing Xposed Installer, nothing can happen.
Click to expand...
Click to collapse
No problem, but as this is a thread for the Installer :angel:

defim said:
In which way inconsistent? Today I was developing with the app causing the IllegalStateException, so it's a debug version. But it is installed and running properly. Maybe some things of it changed since Xposed installer started the 1st time
Click to expand...
Click to collapse
Seems like that IllegalStateException can occur when the app is started while it is being uninstalled. So I imagine that this happened while you were developing and was just a temporary exception. Probably XposedBridge should catch that exception and simple stop doing its stuff, because the starting app will crash anyway.
No problem, but as this is a thread for the Installer :angel:
Click to expand...
Click to collapse
Sure. The problem for the FC is already known and not related to the database-related changes. So now it's just about the "corrupted package" error. Could you please check the MD5 checksum of the APK or redownload it? As the crash happened during the download, maybe the file is simply incomplete. Otherwise, could you get a logcat of the installation attempt? I'm pretty sure that the package manager prints more details in the log.

rovo89 said:
Seems like that IllegalStateException can occur when the app is started while it is being uninstalled. So I imagine that this happened while you were developing and was just a temporary exception. Probably XposedBridge should catch that exception and simple stop doing its stuff, because the starting app will crash anyway.
Sure. The problem for the FC is already known and not related to the database-related changes. So now it's just about the "corrupted package" error. Could you please check the MD5 checksum of the APK or redownload it? As the crash happened during the download, maybe the file is simply incomplete. Otherwise, could you get a logcat of the installation attempt? I'm pretty sure that the package manager prints more details in the log.
Click to expand...
Click to collapse
Yes, just redoing what i did worked. I removed the downloaded file in the "Downloads" app.
Possible that IllegalStateException is caause when Eclipse pushed an apk to the device. But not sure as the log has noe timestamps

Hey guys, just came across this. Hopefully this means Xposed can get rebuilt or whatever to work with ART finally.
http://www.androidpolice.com/2014/0...l-removed-android-art-officially-takes-place/
Sent from my 1961 XP-755

TheKnux said:
ART
Click to expand...
Click to collapse
Please try to find the RED words in the OP...

defim said:
Please try to find the RED words in the OP...
Click to expand...
Click to collapse
Okay, I'm just saying, as the link states, Dalvik is dead.
Sent from my 1961 XP-755

TheKnux said:
Okay, I'm just saying, as the link states, Dalvik is dead.
Sent from my 1961 XP-755
Click to expand...
Click to collapse
rovo89 knows, but would rather it not be mentioned. Whenever ART works with Xposed, we'll know.
Sent from my SCH-I545 using Tapatalk

65vdub said:
rovo89 knows, but would rather it not be mentioned. Whenever ART works with Xposed, we'll know.
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
Alrighty then.
Sent from my 1961 XP-755

Just wanted to say installed this experimental version over 2.6.1 and all is well after installation.

perfect
rovo89 said:
I have just uploaded a test version of Xposed Installer.
If you're already using Xposed and want to help checking for bugs, feel free to download the test version.
Click to expand...
Click to collapse
hi, this is a "no bugs found" report and an opportunity to express my thanks for this great piece of software.

installing the 2.7experimental1 i always got fc of the installer application

Okay, thank you...
Care to share a logcat?

theknut said:
Okay, thank you...
Care to share a logcat?
Click to expand...
Click to collapse
ok i'll take it wait

Bug: Couldn't connect to camera

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

Rear Camera and Flashlight Not Working

UPDATE: Still not working after a complete factory reset (bootlooped option) via Nexus Root Toolkit, and after a battery drain. Here's a fresh logcat on the latest 7.1.1 factory image.
Sometime in the past week or so, my rear camera stopped working completely. The flashlight won't work either. At first, I thought it was a Pure Nexus issue, maybe because I updated to a newer kernel that wasn't compatible with the Pure Nexus build, or perhaps an issue from when I converted /data and /cache to F2FS. However, I've since gone back completely to stock EXT4 and flashed the latest 7.1 factory images directly from Google, and it still doesn't work.
By "doesn't work" I mean that when I try to open the camera app, it immediately says "Camera has stopped". It won't work in other camera apps, or apps that use the rear camera. In fact in other camera apps, I simply won't have the option to switch to the rear camera. Similarly I don't have the Pure Nexus option to long press the power button to turn on the flashlight (which should be there).
I've looked and haven't seen anyone else have the exact same problem. Given I've tried to restore a backup where the camera was working, and then reflashed the latest system images, I'm not sure there's anything else I can do. Maybe it's a hardware issue?
If anyone has any ideas, I'd really appreciate it!
Using a VZW Nexus 6, if that makes any difference. Currently on the latest 1/6 Pure Nexus build with 4.16 ElementalX Kernel.

cowrecked said:
Sometime in the past week or so, my rear camera stopped working completely. The flashlight won't work either. At first, I thought it was a Pure Nexus issue, maybe because I updated to a newer kernel that wasn't compatible with the Pure Nexus build, or perhaps an issue from when I converted /data and /cache to F2FS. However, I've since gone back completely to stock EXT4 and flashed the latest 7.1 factory images directly from Google, and it still doesn't work.
By "doesn't work" I mean that when I try to open the camera app, it immediately says "Camera has stopped". It won't work in other camera apps, or apps that use the rear camera. In fact in other camera apps, I simply won't have the option to switch to the rear camera. Similarly I don't have the Pure Nexus option to long press the power button to turn on the flashlight (which should be there).
I've looked and haven't seen anyone else have the exact same problem. Given I've tried to restore a backup where the camera was working, and then reflashed the latest system images, I'm not sure there's anything else I can do. Maybe it's a hardware issue?
If anyone has any ideas, I'd really appreciate it!
Using a VZW Nexus 6, if that makes any difference. Currently on the latest 1/6 Pure Nexus build with 4.16 ElementalX Kernel.
Click to expand...
Click to collapse
I am sure that with all the info from the basic logcat will help nail down your issues real fast

zelendel said:
I am sure that with all the info from the basic logcat will help nail down your issues real fast
Click to expand...
Click to collapse
good point. here it is.
01-08 15:27:40.878 17520 17541 W CAM_Camera2OneCamMgr: No back-facing camera found.
Click to expand...
Click to collapse
that doesn't look promising

cowrecked said:
good point. here it is.
that doesn't look promising
Click to expand...
Click to collapse
Code:
01-08 15:27:40.991 17520 17520 E AndroidRuntime: FATAL EXCEPTION: main
01-08 15:27:40.991 17520 17520 E AndroidRuntime: Process: com.google.android.GoogleCamera, PID: 17520
01-08 15:27:40.991 17520 17520 E AndroidRuntime: java.lang.NullPointerException: Cannot return null from a [email protected] @Provides method
01-08 15:27:40.991 17520 17520 E AndroidRuntime: at android.support.v4.widget.DrawerLayout$DrawerLayoutCompatImplApi21.checkNotNull(DrawerLayout.java:8048)
01-08 15:27:40.991 17520 17520 E AndroidRuntime: at com.android.camera.hdrplus.HdrPlusModule_ProvidesGcamFactory.get(HdrPlusModule_ProvidesGcamFactory.java:1045)
01-08 15:27:40.991 17520 17520 E AndroidRuntime: at dagger.internal.DoubleCheck.get(DoubleCheck.java:47)
01-08 15:27:40.991 17520 17520 E AndroidRuntime: at com.android.camera.hdrplus.HdrPlusPrewarmBehavior.run(HdrPlusPrewarmBehavior.java:42)
01-08 15:27:40.991 17520 17520 E AndroidRuntime: at com.android.camera.behavior.Behaviors$1.run(Behaviors.java:47)
01-08 15:27:40.991 17520 17520 E AndroidRuntime: at com.google.android.apps.camera.async.MainThreadThrowingExecutor$MainThreadThrowingRunnable.run(MainThreadThrowingExecutor.java:21)
01-08 15:27:40.991 17520 17520 E AndroidRuntime: at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:428)
01-08 15:27:40.991 17520 17520 E AndroidRuntime: at java.util.concurrent.FutureTask.run(FutureTask.java:237)
01-08 15:27:40.991 17520 17520 E AndroidRuntime: at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:272)
01-08 15:27:40.991 17520 17520 E AndroidRuntime: at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1133)
01-08 15:27:40.991 17520 17520 E AndroidRuntime: at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:607)
01-08 15:27:40.991 17520 17520 E AndroidRuntime: at java.lang.Thread.run(Thread.java:761)
01-08 15:27:40.991 17520 17520 E AndroidRuntime: at com.google.android.apps.camera.async.AndroidPriorityThread.run(AndroidPriorityThread.java:32)
There are tons of errors in that logcat. From modem errors to art errors. Which is what this seems to be. With at least the log maybe someone will have an idea.

Just completely reset my phone back to stock on the latest 7.1.1 factory image using the Nexus Root Toolkit. Here's a 2nd logcat attempting to access the camera.

cowrecked said:
Sometime in the past week or so, my rear camera stopped working completely. The flashlight won't work either. At first, I thought it was a Pure Nexus issue, maybe because I updated to a newer kernel that wasn't compatible with the Pure Nexus build, or perhaps an issue from when I converted /data and /cache to F2FS. However, I've since gone back completely to stock EXT4 and flashed the latest 7.1 factory images directly from Google, and it still doesn't work.
By "doesn't work" I mean that when I try to open the camera app, it immediately says "Camera has stopped". It won't work in other camera apps, or apps that use the rear camera. In fact in other camera apps, I simply won't have the option to switch to the rear camera. Similarly I don't have the Pure Nexus option to long press the power button to turn on the flashlight (which should be there).
I've looked and haven't seen anyone else have the exact same problem. Given I've tried to restore a backup where the camera was working, and then reflashed the latest system images, I'm not sure there's anything else I can do. Maybe it's a hardware issue?
If anyone has any ideas, I'd really appreciate it!
Using a VZW Nexus 6, if that makes any difference. Currently on the latest 1/6 Pure Nexus build with 4.16 ElementalX Kernel.
Click to expand...
Click to collapse
Flash back to stock completely. see if the drivers will show your camera.

zmedhaug said:
Flash back to stock completely. see if the drivers will show your camera.
Click to expand...
Click to collapse
Had you bothered to read you would have seen he did that already.

zelendel said:
Had you bothered to read you would have seen he did that already.
Click to expand...
Click to collapse
Yeah i read it. i said completely. key word. i mean hook up this bad boy to wugfresh, click on Soft-Bricked/Bootlooped. Flash stock and use the file Wugfresh downloads. i dont mean flash from twrp.

I'm thinking it was the "not completely compatible" kernel that you used. same thing happened to my Chromebook while I was messing around with it. I would recommend to drain the battery completely to hopefully reset the camera module.

Thanks guys, I'll try completely completely resetting it tonight, and if that doesn't work I'll drain it

cowrecked said:
Thanks guys, I'll try completely completely resetting it tonight, and if that doesn't work I'll drain it
Click to expand...
Click to collapse
Wait...
Did you ever wipe all your data... Or are you being lazy and just reflashing the system image?
I've never heard of draining the battery fixing a software issue... But really... What do I know...
Rather than unnecessarily draining your battery... Get fresh images from Google... Check the md5... Then flash all the parts individually with fastboot... Not a toolkit... Yes... Even data and cache...
If that doesn't fix the issue... Get fresh logs...

rignfool said:
Wait...
Did you ever wipe all your data... Or are you being lazy and just reflashing the system image?
I've never heard of draining the battery fixing a software issue... But really... What do I know...
Rather than unnecessarily draining your battery... Get fresh images from Google... Check the md5... Then flash all the parts individually with fastboot... Not a toolkit... Yes... Even data and cache...
If that doesn't fix the issue... Get fresh logs...
Click to expand...
Click to collapse
Yes, of course I've wiped all of my data. Multiple times. I even formatted /data and /cache to F2FS, and then back to ext4. And I've both installed images using fastboot, and using the root toolkit. No luck so far.
I did post fresh logs yesterday, but I'll post even fresher ones to the OP in a sec.
Oh, and I let the battery drain just now, that didn't fix it either.
EDIT: Here's the fresh logcat on the 7.1.1 factory images, installed via fastboot.

I don't think this is a software issue, but hardware. Either the camera module has failed, or the motherboard connector failed. I think it was only a coincidence that it happened on Android 7.x, and I'm willing to guess installing an older version of Android will make no difference.

Strephon Alkhalikoi said:
I don't think this is a software issue, but hardware. Either the camera module has failed, or the motherboard connector failed. I think it was only a coincidence that it happened on Android 7.x, and I'm willing to guess installing an older version of Android will make no difference.
Click to expand...
Click to collapse
At this point, I'm pretty much resigned to having a Nexus 6 without a working camera. I agree, I'm not sure what else I can do software-wise to try to fix it.
Luckily, I've got a Pixel XL arriving at the end of the month, but I was really hoping to have a solid backup/2nd device :/

Well, if it's only the camera itself and not the motherboard, you could replace the camera module yourself. But otherwise...yeah.

Having same issue - Different phone, happened week after 7.1.1 update.
---------- Post added at 06:26 PM ---------- Previous post was at 06:23 PM ----------
I finally just found Android 6.0 ROM and flashed that onto backup phone having issues. It began working like it should.