Database Develop

[DEV] GoogleTV: Netflix and Chrome port? Possible?

Ok, so I have been on a mission this afternoon. I figured I wanted Netflix on this phone BEFORE it's official. So, after a little google-fu, I found the Logitech Revue has it on there. I also found there was a system dump for this guy. I have attached the link to Multi upload for the system dump and all I have messed with so far.
Sooooo, here we go
So far here's what I have done:
1) Deodex Netflix.apk and Resigned it
2) Deodex the com.google.tv.preference.jar
3) moved files netflixclient.so to LIBs folder
4) moved the google.tv.pref from above to the framework folder. No go..
5) tried to install NetflixAPK--> get the below error and it fails.
Here is the logcat I get when I try to install-
Code:
03-07 15:39:00.073 4402 4402 V PaperForest: Time at selected location now 15.65
03-07 15:39:00.073 4402 4402 V PaperForest: Sunrise Start = 6.3333335hrs, Sunrise End = 6.8333335hrs
03-07 15:39:00.073 4402 4402 V PaperForest: Sunset Start = 18.5hrs, Sunset End = 19.0hrs
03-07 15:39:00.073 4402 4402 V PaperForest: Daylight level (0 - 1.0) = 1.0
03-07 15:39:00.073 4402 4402 V PaperForest: Sun ray angle = 21 deg
03-07 15:39:02.583 1497 1510 D StatusBarPolicy: mSignalStrength=SignalStrength: 25 -1 -1 -1 -1 -1 -1 gsm 5 -63 -9
03-07 15:39:02.583 1497 1510 D StatusBarPolicy: raw_sig_level=-63,raw_ecno_ber=-9,raw_rat=5
03-07 15:39:02.583 1497 1510 D StatusBarPolicy: rscp_iconLevel=5, ecno_iconLevel=5
03-07 15:39:02.583 1497 1510 D StatusBarPolicy: iconLevel = 5
03-07 15:39:02.753 1497 4472 I ActivityManager: Starting activity: Intent { dat=file:///mnt/sdcard/Netflix.apk cmp=com
.android.packageinstaller/.InstallAppProgress (has extras) }
03-07 15:39:02.933 6687 6693 D dalvikvm: GC_EXPLICIT freed 274 objects / 17056 bytes in 86ms
03-07 15:39:02.943 1497 1525 D PackageParser: Scanning package: /data/app/vmdl12358.tmp
03-07 15:39:03.033 1497 1525 D PackageManager: Scanning package com.google.tv.netflix
03-07 15:39:03.033 1497 1525 E PackageManager: Package com.google.tv.netflix requires unavailable shared library com.google.tv.preference; failing!
03-07 15:39:03.033 1497 1525 W PackageManager: Package couldn't be installed in /data/app/com.google.tv.netflix-1.apk
03-07 15:39:03.153 1497 1525 D dalvikvm: JIT code cache reset in 2 ms (1048548 bytes 1/0)
03-07 15:39:03.153 1497 1525 D dalvikvm: GC_EXPLICIT freed 23634 objects / 950176 bytes in 115ms
03-07 15:39:03.173 1497 3815 I ActivityManager: Displayed activity com.android.packageinstaller/.InstallAppProgress: 3
78 ms (total 378 ms)
03-07 15:39:03.653 1411 1520 I : odm_disp_esd_thread is running(27) state=1
You can see that it fails here:
03-07 15:39:03.033 1497 1525 E PackageManager: Package com.google.tv.netflix requires unavailable shared library com.google.tv.preference; failing!
After some googling I came up with:
http://markmail.org/message/hiunm2r3llri7exi
It basically says I need to add a ref to the manifest file.. but which one/where!? This is where I need a "experienced" dev to step in I think..
so my question is how do I resolve/add that? Is the libs even required? There are a few other files people seem to think are needed but I just want to get it to install first.
Am I beating down a lonely path only to find a failboat? am I wasting my time? I think this would be awesome to get done on our devices, I am just coming to a screeching halt atm. Any info/help would be SUPER APPRECIATED.
Another neat one to have on our device from the Revue's system dump- CHROME
GooglTV's System Update Dump:
http://www.multiupload.com/ZVCUX5MSBB
http://www.multiupload.com/REVEQS6HII - mirror
Attached to thread: Allt he files I am messing with- deodexed APK, libs, and jar. See here for a better version of the deodexed files.

MANIFEST.MF gets updated with filenames and SHA1 hashes when you sign the apk. I'm not quite sure as to how to tell it which files should go in there, as it doesn't include everything.

03-07 15:39:03.033 1497 1525 E PackageManager: Package com.google.tv.netflix requires unavailable shared library com.google.tv.preference; failing!
You need to grab that framework file from where ever you got the netfilx apk.
----
ya, and i just now read the rest of your post, you have done that already

maybe I did something wrong?
I grabbed the com.google.tv.prefence.jar from the framework folder- do I need the odex? Do I need to deodex the jar?

malfuncion said:
maybe I did something wrong?
I grabbed the com.google.tv.prefence.jar from the framework folder- do I need the odex? Do I need to deodex the jar?
Click to expand...
Click to collapse
ya, you need the odex and the jar, deodex them, then I bet it would work

I started over from scratch cause I think the netflix apk was messed up- same results. here's the steps I went through-
1) I re-deodexed the netflix and com.google.tv.preference.jar - I attached them to this reply for anyone else who wants to give it a go
2) Moved the jar to the system/framework then set permissions back
3) Tried to install via ADB and by pushing it. I have tried to stick it in the system/app/ dir and reboot- still notta.
What else could it be? Think I could be missing some other dependencies? It keeps crying about the preference but its there..?

You are missing about 60mb worth of netflix files
http://pastebin.com/Gt2G8paT
got it going further, but now I have no clue

Unable to dlopen(/system/lib/libnetflixclient.so): Cannot load library: link_image[2046]: failed to link libnetflixclient.so
did you copy over the .so files?
which files am I missing to get it to that point? I have that system update dump downloaded to this box?

malfuncion said:
Unable to dlopen(/system/lib/libnetflixclient.so): Cannot load library: link_image[2046]: failed to link libnetflixclient.so
did you copy over the .so files?
which files am I missing to get it to that point? I have that system update dump downloaded to this box?
Click to expand...
Click to collapse
here ya go
http://www.mediafire.com/?1ijbm4pj3vjt6kc

are you trying to execute the apk or did you fire off the start-netflix-service script? I was looking at that script and it has parts about INTEL specific SDK. if those are related I dont think this thing will work...

Im interested in the Chrome Dump
You know, replacing Firefox with it in webtop

If youa re interested in the chrome part- here is what another member has done..
http://forum.xda-developers.com/showpost.php?p=9573308&postcount=3
Basically sent all dependencies and got stuck in a bootloop....
As for netflix- it looks like it has a service that starts in the background for DRM. This service may be portable, but it is beyond me as it calls some Intel Specific SDK options. I think the apk (app) calls on the service whenever you want to watch a movie. THe service brings the movie in, and then mirrors output to the app. This is what I getting from a few scripts, I may be WAAAAY off base here though. I think we may have a good possibility of porting the netflix app to webtop and maybe chrome, if someone wants to take a stab at it. I took it as far as I could, @DG- you get any further?

aren't those programs meant to work on an x86 application (most google tv boxes that I've seen use intel atom processors). Wouldn't it be a pita to get them working on our ARM phones?

you are correct, the GoogleTV is an intel device. There are certain scripts in the dump that reflect that. However there are other instances that call the Android API solely to which we may be able to port them. The intel part is more specific to drivers and the way android OS interacts with the system. Still, laying inside there is true android and DEVs are currently working to port normal apps to gTV
I am not so sure if Chrome is one of them that uses x86 API's or not. I was mainly focused on the netflix part. from some of the structure of the zip it does look like Chrome is in the same boat as Netflix.
The netflix is going to be a PITA in of itself without some MAJOR help. I think even if we ported it- it would be a moot point as we will probably get a REAL working Netflix before anyone made major headway with this one.

malfuncion said:
The netflix is going to be a PITA in of itself without some MAJOR help. I think even if we ported it- it would be a moot point as we will probably get a REAL working Netflix before anyone made major headway with this one.
Click to expand...
Click to collapse
Don't mean to sh#t in yer Wheaties but from what I understand the Netflix app is going to require a drm signature specifically from snapdragon processors to work....not a dev but heres a link to the article I read...http://www.talkandroid.com/30458-ne...ws,+Rumours,+and+Updates)&utm_content=Twitter
Sent from my MB860 using XDA App

robonoob said:
Don't mean to sh#t in yer Wheaties but from what I understand the Netflix app is going to require a drm signature specifically from snapdragon processors to work....not a dev but heres a link to the article I read...http://www.talkandroid.com/30458-ne...ws,+Rumours,+and+Updates)&utm_content=Twitter
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
dont mean to sound like a douche, but did you not read the thread? Look about 3 posts up, this was covered. Netflix runs a service(script) that handles the DRM for the GTV. That script seems to pull in the media from netflix, auth it, then pipe it to the app. Without porting the service over the app is worthless. Netflix will come up with a solution before we will, thats a given.
As for the continuing of the thread, I am currently looking at the Chrome piece. However, like mentioned in another thread, I too get stuck at the stale dependencies. Chrome looks to be bust on this as well.

malfuncion said:
dont mean to sound like a douche, but did you not read the thread? Look about 3 posts up, this was covered. Netflix runs a service(script) that handles the DRM for the GTV. That script seems to pull in the media from netflix, auth it, then pipe it to the app. Without porting the service over the app is worthless. Netflix will come up with a solution before we will, thats a given.
As for the continuing of the thread, I am currently looking at the Chrome piece. However, like mentioned in another thread, I too get stuck at the stale dependencies. Chrome looks to be bust on this as well.
Click to expand...
Click to collapse
Sorry no disrespect didn't see that post above...
Sent from my MB860 using XDA App

Netflix has code for the Snapdragon...
I looked around a bit on the neet looking at netflix on android. It appears that they have placed a NetFlix app one an LG Revolution at CES. It this is legit, and we can get a copy of the app, we should have almost everything we need to run netflix on the Atrix.
I had a link here, but I'm too new to the forum to post it :-(
The LG Revolution uses a Snapdragon MSM8655 CPU (Cortex 8 I believe). The Atrix also uses a Snapdragon CPU, the Cortex 9.
According to ARM, "the scalable Cortex-A9, the market-proven Cortex-A8 processor, and the high-efficiency Cortex-A5 processors all share the same architecture and therefore full application compatibility." (Anther missing link, you should be able to google this one easily).
So, if we can get our hands on the NetFlix app that was running on the that or another LG Revolution, we will be in business. This way we are dealing with code that should execute natively on the Atrix CPU.
Anyone down for hunting? I'd expect that NetFlix hasn't put this "beta" on many phones yet, so it might not be easy to track it down and dump it, but if anyone has any ideas or a way, I'd appreciate it.

jay_tea said:
The Atrix also uses a Snapdragon CPU, the Cortex 9.
Click to expand...
Click to collapse
The Atrix does not use a Snapdragon CPU.
It uses an NVIDIA Tegra 2 Cortex A9 dual core CPU.

yeah, netflix has been discussed in the EVO forums IIRC, and as expected its using C code that has been compiled for x86, which is obviously not going to work on any current android phone, even if the APK doesn't have x86 code, some of the libraries or other dependencies will. As for Chrome, I'd think it would have to have x86 compiled C code as its not like they rewrote everything in java

[ROM] CM 10.1(Android 4.2) for Atrix

This is a CM10 .1 (Jelly Bean, Android 4.2) firmware for Atrix. It's not a official CyanogenMod, and it's not supported by CM team.
Disclaimer: THIS FIRMWARE IS IN ALPHA STAGE OF DEVELOPMENT.
I'm not responsible by phone bricks of any kind, or any other damage this firmware may cause to you, to your phone or any accessories conected to your phone.
Click to expand...
Click to collapse
All installation procedures are the same as for CM9 and CM10.
MAKE A BACKUP OF YOUR CURRENT FIRMWARE SO YOU CAN RETURN IF YOU WANT.
This ROM uses the kernel 3.1.10, from Olympus Kernel Project: http://forum.xda-developers.com/showthread.php?t=2016837
For changelog, download links, credits, notes and tips, see my website
http://www.linuxmobile.org/atrix/cm10-1
Thanks to all the users for using and debugging. If you want to support my work donating, click the donate button(below my avatar), or in my website.
THANKS TO THE DONATORS. THANKS VERY MUCH.

EPinter you are truly the man.
Sent from my olympus using xda premium

If it boots, we're thankful for it! Thanks Bill and epinter! The ROM Kings and our kernel devs make for quite the team.

Just flashing for 2 times, booted successfully but com.google.process.gapps stopped. i flashed v5 gapss.

Awesome,,,,
Thanks for keeping it going ! Will the new moto xphone have a sdcard?? if not this willl be my phone for a long long time Keep it up Testing now...

epinter said:
Backup before install. Installation procedure is the same as the CM10.
Click to expand...
Click to collapse
What exactly is installation procedure, e.g. coming from non-cm-based?
Sent from my MB860 using xda premium

Installed, booted, working.
Can't find a play store that works, nor gapps. Looks like Wi-Fi and phone signal indications are not showing bars. However, both Wi-Fi and phone are working.
Thanks for your continuing efforts!!

Excellent work!!!
Thank you very much...
Enviado desde mi Motorola Atrix

Thank you for your hard work :thumbup:
Inviato dal mio motoFAIL MB860 tramite Tapatalk

Oh my god
You're best developer ever
Sent from my MB860 using xda premium

you r awesome

Truly the master of android
for people who want gapps, you have to install the correct gapps (hence 4.2.1)
Keep in mind that this zip file is too big for our system partition and will probably result in some fc's as well, but untill epinter makes an appropriate gapps this will do i believe
I installed this one and no fc's of android apps untill now, play store also working for me.
edit: Only FC untill now related to alarms/clock.
logcat:
Code:
--------- beginning of /dev/log/main
I/ ( 1406): odm_disp_cabc_thread running
I/ ( 1406): odm_disp_cabc_thread is restarting err_cnt=69
W/dalvikvm(23647): threadid=12: thread exiting with uncaught exception (group=0x40a89930)
I/ActivityManager( 1787): Displayed com.android.deskclock/.AlarmClock: +171ms
--------- beginning of /dev/log/system
I/ActivityManager( 1787): START u0 {cmp=com.android.deskclock/.AlarmClock} from pid 23647
E/AndroidRuntime(23647): FATAL EXCEPTION: AsyncTask #1
E/AndroidRuntime(23647): java.lang.RuntimeException: An error occured while executing doInBackground()
E/AndroidRuntime(23647): at android.os.AsyncTask$3.done(AsyncTask.java:299)
E/AndroidRuntime(23647): at java.util.concurrent.FutureTask.finishCompletion(FutureTask.java:352)
E/AndroidRuntime(23647): at java.util.concurrent.FutureTask.setException(FutureTask.java:219)
E/AndroidRuntime(23647): at java.util.concurrent.FutureTask.run(FutureTask.java:239)
E/AndroidRuntime(23647): at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1080)
E/AndroidRuntime(23647): at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:573)
E/AndroidRuntime(23647): at java.lang.Thread.run(Thread.java:856)
E/AndroidRuntime(23647): Caused by: android.database.sqlite.SQLiteException: Can't downgrade database from version 7 to 5
E/AndroidRuntime(23647): at android.database.sqlite.SQLiteOpenHelper.onDowngrade(SQLiteOpenHelper.java:361)
E/AndroidRuntime(23647): at android.database.sqlite.SQLiteOpenHelper.getDatabaseLocked(SQLiteOpenHelper.java:255)
E/AndroidRuntime(23647): at android.database.sqlite.SQLiteOpenHelper.getReadableDatabase(SQLiteOpenHelper.java:188)
E/AndroidRuntime(23647): at com.android.deskclock.AlarmProvider.query(AlarmProvider.java:72)
E/AndroidRuntime(23647): at android.content.ContentProvider.query(ContentProvider.java:652)
E/AndroidRuntime(23647): at android.content.ContentProvider$Transport.query(ContentProvider.java:189)
E/AndroidRuntime(23647): at android.content.ContentResolver.query(ContentResolver.java:372)
E/AndroidRuntime(23647): at android.content.CursorLoader.loadInBackground(CursorLoader.java:65)
E/AndroidRuntime(23647): at android.content.CursorLoader.loadInBackground(CursorLoader.java:43)
E/AndroidRuntime(23647): at android.content.AsyncTaskLoader.onLoadInBackground(AsyncTaskLoader.java:301)
E/AndroidRuntime(23647): at android.content.AsyncTaskLoader$LoadTask.doInBackground(AsyncTaskLoader.java:68)
E/AndroidRuntime(23647): at android.content.AsyncTaskLoader$LoadTask.doInBackground(AsyncTaskLoader.java:56)
E/AndroidRuntime(23647): at android.os.AsyncTask$2.call(AsyncTask.java:287)
E/AndroidRuntime(23647): at java.util.concurrent.FutureTask.run(FutureTask.java:234)
E/AndroidRuntime(23647): ... 3 more
W/ActivityManager( 1787): Force finishing activity com.android.deskclock/.AlarmClock
W/ActivityManager( 1787): Force finishing activity com.android.deskclock/.DeskClock
D/dalvikvm( 2853): GC_CONCURRENT freed 378K, 33% free 3140K/4652K, paused 2ms+3ms, total 30ms

aaurnab said:
Just flashing for 2 times, booted successfully but com.google.process.gapps stopped. i flashed v5 gapss.
Click to expand...
Click to collapse
Flash gapps from goo.im. I tested those on the to be released Photon build as well as the Atrix build I've been working on
LOL! I post right below the comment with the link...excellence there

very very smooth rom but camera not work. thanks epinter.

I will make a gapps package, the package from goo fills the /system.

jorno88 said:
Truly the master of android
for people who want gapps, you have to install the correct gapps (hence 4.2.1)
Keep in mind that this zip file is too big for our system partition and will probably result in some fc's as well, but untill epinter makes an appropriate gapps this will do i believe
I installed this one and no fc's of android apps untill now, play store also working for me.
edit: Only FC untill now related to alarms/clock.
logcat:
E/AndroidRuntime(23647): Caused by: android.database.sqlite.SQLiteException: Can't downgrade database from version 7 to 5
[/CODE]
Click to expand...
Click to collapse
This kind of error you can solve cleaning the app data.

Very impressive indeed.
Any thoughts about symbolic linking the unused /osh partition under /system for much additional all space?
Sent from my MB860 using Tapatalk 2

Oh god ur the man
Sent from my MB860 using xda premium

wow!! I didn't ever thought that the 4.2 will ever come to our phone!!
thank you epinter! you are awsome man!!
you keep this phone alive!!

greatt
Than you for your hard work man!!
Will give feddback in a few hours!:good:
First thing i've noticed is that i get a blank screen when try to use the camera.. will wait until it works..
EDIT: you can take pics, but you will not be able to see them unless you enter the galery!
thanks!

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