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

[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.

[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!

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.

Duplicate finish request for ActivityRecord ( when user close the interstatial ads )

07-17 22:37:53.457 1731-2110/system_process W/ActivityManager: Duplicate finish request for ActivityRecord{cd38804 u0 lawinmyhand.ipcindianpenalcode/com.google.android.gms.ads.AdActivity t220 f}

probably when the user is closing the ad, your activity is already destroyed so you get this Duplicate finish error.

so , there is no problem in implementing it and publishing it
Unity Dev said:
probably when the user is closing the ad, your activity is already destroyed so you get this Duplicate finish error.
Click to expand...
Click to collapse
so , there is no problem in implementing it and publishing it

waqaralamlive said:
so , there is no problem in implementing it and publishing it
Click to expand...
Click to collapse
you can check if getActivity() returns null, then you do not execute the code which finishes the activity