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
Related
An official OTA for GSM Nexus S (GT-i9020T/i9023) is now available:
http://android.clients.google.com/packages/ota/google_crespo/9ZGgDXDi.zip (thanks bl1nkk)
Because an official release is now available, this ROM is now EOL and will receive no further support.
By popular demand, here's a new thread for my port of the Jelly Bean SDK. This is a continuation of DaxMax's thread, so if you want to see previous discussion, look there. (Thanks to DaxMax for putting up with discussion of what is essentially a distant cousin of his original ROM for so long on his thread.)
http://files.mrks.me/update-crespo-JRN83C-preview-2012063001.zip http://goo.gl/40Cxf (thanks to bl1nkk for the hosting)
Code:
MD5: 015e322b048b7e1464a90a87a5a6bcb1
SHA1: 3aca40900b40625505d4b6c0afce93c31e33770d
SHA256: 3b0b76444c307f4ffe685205cb92ad6060d957152dadef72444b3f2407510a34
Service Pack 4 for this ROM: https://docs.google.com/uc?export=download&id=0BwGWbMaI9twWRHFrRUROcDhIeVk http://goo.gl/ZVlQS (many thanks to bl1nkk for hosting) (alternately, check thread for mirrors) (see this post for changelog)
Code:
MD5: ac85b1e309ba3a3f438efe0954c11c32
SHA1: d147f777f8594c5d33dfd480143758107ff1baab
SHA256: 951d39e75e8d4891e18a1da3896567f293074262d8aef3cd0021d4239492cf00
Flash the main ROM zip (update-crespo-JRN83C-preview-2012063001.zip) first, then the service pack.
These are zips which should be flashable from ClockworkMod or other recovery. They contain /system and a boot.img and will not touch your recovery, data, or SD card. I believe you need to do a full wipe if you're flashing over ICS or below.
This ROM is quite stable and almost fully working at this point. Highlights:
Based on the Jelly Bean SDK release (JRN83C), with Google apps and other components from the Nexus 7 factory image (JRN84D). Hardware-related files and kernel from the ICS IMM76D release for Nexus S. (The source for the GPL components (mainly the kernel) is available from http://android.googlesource.com/.) The wifi hack (libhardware_legacy.wifi.so) is posted farther down this thread (including source).
Remarkably smooth. Project Butter really lives up to its name. (I've made one tweak in the init.herring.rc to make the default ICS cpufreq governor more aggressive in upping the clock frequency, in order to simulate the change in governor in the Jelly Bean kernel.)
Wifi, Bluetooth, GPS, GSM all work. NFC should work.
Sound and calls work as of July 9 (SP1).
Video recording works as of July 10 (SP2).
Tethering, including wifi tethering, works as of July 11 (SP3).
Calls via a Bluetooth headset work as of July 11 (SP3).
Google Now/voice search, offline voice text input, voice dialing, and text-to-speech all work as of July 11 (SP4).
Broken:
Voice/video chat in Google Talk Patch available to fix video/voice chat, see this post. (thanks selectormoldy for the crash log leading to fix)
Media scanning (used by Gallery and Music to find files on the SD card, among other things) is broken for some, but not for others. This appears to be triggered by something stored on the SD card/external storage. (thanks spupuz)
High-performance WifiLocks (the wifi driver drops into low-power mode when the screen turns off, even though it shouldn't when a high-perf WifiLock is held).
Sound. Note that means no phone calls of any kind, not even emergency calls, so this isn't ready for serious day-to-day use. This is likely unreasonably difficult to solve given that we have an official OTA coming in 2-3 weeks; look upthread for an account of what's been tried.
Ambient light sensor. It worked in the Galaxy Nexus-based ROM, and I'm not sure why it doesn't work in this one; in any event I'm not planning on putting more time into figuring out why. The light sensor works, but automatic brightness setting does not -- presumably something in the Android framework needs to be changed.
Video recording (as reported by users in this thread).
The Google Now/Google Search app may crash (reported by users in this thread). (This should be fixed in SP3 -- if you're still having problems, please provide a logcat.)
Tethering via wifi.
Phone calls via Bluetooth.
Voice dialing.
Voice search in Google Now. (The app fails to recognize when you stop speaking, so the search is never performed.)
Text-to-speech functionality with Google TTS (Pico TTS works).
Notes:
If the first-run setup keeps crashing on you: from the language selection (first) screen, tap on the four corners of the screen, proceeding clockwise from top left. This will bypass the first-run setup; you can then set up a Google account manually in Settings. (thanks urko95) (If you are still experiencing this with SP4, please report in this thread. A logcat would be helpful.)
Note also that there won't be much in the way of support -- I do have other things that I really should be doing ...
Service Pack 4
Service Pack 4 for the 2012/06/30 SDK JRN83C ROM. This can be flashed on top of the original JRN83C ROM with or without any of the previous service packs applied.
https://docs.google.com/uc?export=download&id=0BwGWbMaI9twWRHFrRUROcDhIeVk http://goo.gl/ZVlQS (many thanks to bl1nkk for hosting) (alternately, check thread for mirrors)
Changes in SP4:
Added the files in /system/usr/srec/en-US from the Nexus 7 JRN84D factory image -- Google Now/voice search, voice dialing, and offline voice dictation input all work.
Added /system/lib/libpatts_engine_jni_api.so from the Nexus 7 JRN84D factory image -- Google TTS now works. (Pico TTS already worked in previous releases.)
Replaced /system/app/SetupWizard.apk with the version from the Galaxy Nexus JRN84D build -- first-run setup should now display properly. (For the curious, I got the apk from Koush's jb-takju.zip and verified that it matched the JRN84D OTA via the SHA1 sums in the OTA update package.)
Added /system/app/{LiveWallpapers,VisualizationWallpapers,HoloSpiralWallpaper}.apk from Nexus S IMM76D to provide some live wallpapers.
Reverted a change in /system/framework/framework-res.apk to the default wallpaper; defaulting to the Nexus live wallpaper hurts performance.
Changes in SP3 (included in SP4):
libhardware_legacy.wifi.so updated to support wifi tethering. (See the linked post for source code.)
Permissions on /system/etc/bluetooth fixed to allow BlueZ to see its config files -- fixes phone calls over a Bluetooth headset, plus lots of other Bluetooth-related functionality.
hwcomposer.s5pc110.so replaced with a build from Jelly Bean-based source -- hopefully fixes hwcomposer bugs people have been experiencing. (See this post for more information.)
Removed /system/app/QuickSearchBox.apk to prevent conflicts with Google Now -- should fix Google Now access for most people. If you're still seeing problems, please provide a full logcat. (thanks afzalarsalan)
Changes in SP2 (included in SP3 and later):
New boot.img with /init.herring.rc edited to fix a thinko which was preventing CPU governor tweak from taking effect -- should result in more smoothness.
/system/build.prop edited to report as a "user" build instead of an "eng" build -- resolves red border flashing on screen. (thanks capez)
/system/etc/media_codecs.xml and /system/etc/media_profiles.xml copied from the Jelly Bean device/samsung/crespo tree -- video recording now works.
/system/lib/libjni_mosaic.so copied from Nexus 7 JRN84D image -- panoramic camera now works.
More changes from Nexus S ICS /system/framework/framework-res.apk integrated -- automatic brightness setting now enabled, tethering menu now enabled (wifi tethering is still broken).
Changes in SP1 (included in SP2 and up):
Jelly Bean audio HAL modules included -- sound now works.
/system/build.prop edited to report as a "user" build instead of an "eng" build -- resolves red border flashing on screen. (thanks capez) I screwed up integrating this fix, so it's not actually part of SP1. Will be in SP2.
/system/bin/make_ext4fs and /system/bin/setup_fs replaced with Nexus 7 JRN84D binaries -- fixes installing apps to SD card. (thanks smojica for reporting)
Removed LegacyCamera app to avoid having two camera apps.
Code:
MD5: ac85b1e309ba3a3f438efe0954c11c32
SHA1: d147f777f8594c5d33dfd480143758107ff1baab
SHA256: 951d39e75e8d4891e18a1da3896567f293074262d8aef3cd0021d4239492cf00
This is safe to flash on top of your ROM, whether or not you have any of the previous service packs installed.
I'll probably continue to distribute updates to this ROM via these service packs, mostly to save everyone bandwidth. (As with MS Windows service packs, they will be cumulative -- e.g. SP5, assuming there is one, will be flashable on top of the base ROM or any of SP1-4.)
FAQ
Frequently Asked Questions:
Did you see that the Jelly Bean source is out?
Yes -- and we're using it to provide audio, among other things. It was faster to use bits and pieces of the source to fix the SDK port than it was to sync and build the whole thing from source -- particularly since Google has not released proprietary blobs matching Jelly Bean for the Nexus S yet.
How do I get root?
The same way you do on a stock ROM -- flash Superuser. (thanks DaxMax)
The first-run setup keeps crashing!
From the language selection (first) screen, tap on the four corners of the screen, proceeding clockwise from top left. This will bypass the first-run setup; you can then set up a Google account manually in Settings. (thanks urko95)
Google Now crashes when I try to use GPS/navigation!
Install Google Maps from Market. (Several of the standard Google apps were not included in the base ROM to save download time.) (thanks legolas93)
My language is something other than US English, and offline speech recognition/voice input doesn't work!
Google's only implemented offline speech recognition for US English at the moment -- all other languages (including other English variants) still rely on Google servers to perform speech recognition.
I can't install the XDA app.
I can't install apps to SD card!
Flash Service Pack 1 or later.
I flashed http://www27.zippyshare.com/v/48676662/file.html, and I still can't install apps to SD card!
Flash Service Pack 1 or later. That zip only includes audio HAL modules and a fix for the red flashes on screen, not the rest of the SP1 bugfixes.
What are those red flashes on screen?
Video recording doesn't work!
Where's the tethering menu?
Flash Service Pack 2 or later.
The bar at the top of the home screen doesn't launch Google Now!
Wifi tethering doesn't work!
My Bluetooth headset/hands-free kit can't be used in phone calls!
Flash Service Pack 3 or later.
Google Now doesn't recognize when I stop talking!
Text-to-speech doesn't work!
Why is "Welcome" in the first-run setup screen so giant?
Flash Service Pack 4 or later.
I flashed 1337kernel, and now XYZ doesn't work!
See this post by Oodie for advice.
XXX/YYY/ZZZ doesn't work!!!!!!
Make sure you've done a full wipe (including data) and flashed the ROM correctly (base ROM, then the latest service pack). Try using the stock kernel included with this ROM; people have reported problems using custom kernels, particularly with sound. If the problem persists, pleave provide a detailed description of the problem and a logcat so that we can help you.
Why not do a full build from source?
This was quicker for me and works quite well. That said, anyone who wants to attempt a build from AOSP and/or CM10 source is welcome to do so, and I'll be happy to answer any questions that may come up in the process.
From the first 30 minutes playing with it.. Google Search / Now takes into account what your saying but doesnt do anything with the data - But doesnt seem to crash with SP1 Also a little big laggy here and there. But pretty much perfect. EXCELLENT ROM Steven676. I have been so excited for this release Thankyou!!
EDIT: Also get a red flash around screen when unlocking phone (still not a huge thing) :]
Looks great, thank you!
So flash the rom, then flash the service pack in op and then service pack in second post?
g1user101 said:
So flash the rom, then flash the service pack in op and then service pack in second post?
Click to expand...
Click to collapse
Both are the same, as I understand
Flashed to SP1 half a day ago and it was rocking! Kudos for this! :good:
I tried flashing GN's JB-SuperSU.zip, it seems to be incompatible (constantly crashing on the permission dialog). Anyone got ideas of how to get root?
nice thread !! i want to try it but i use the Phone calls via Bluetooth on my car radio !! i cant make call when the bluetooth connect on my car radio ?
thanks
thanr said:
Flashed to SP1 half a day ago and it was rocking! Kudos for this! :good:
I tried flashing GN's JB-SuperSU.zip, it seems to be incompatible (constantly crashing on the permission dialog). Anyone got ideas of how to get root?
Click to expand...
Click to collapse
Superuser - Download it and flash it.
DaXmax said:
Superuser - Download it and flash it.
Click to expand...
Click to collapse
Worked
cant bypass the setup screen, tapping 4 corners does nothing? no idea
Bringing over some other tidbits from the other thread about what's broken in SP1:
Automatic brightness setting. I've checked that the ambient light sensor works through another app, so presumably something in the Android framework is missing.
Video recording. Trying to start video recording turns up this set of errors:
Code:
V/videocamera( 2240): startVideoRecording
D/CameraStorage( 2240): External storage state=mounted
V/videocamera( 2240): initializeRecorder
W/StagefrightRecorder( 97): Max file duration is not positive: 0 us. Disabling duration limit.
W/StagefrightRecorder( 97): Target duration (0 us) too short to be respected
V/videocamera( 2240): New video filename: /mnt/sdcard/DCIM/Camera/VID_20120710_025327.mp4.tmp
D/CameraSource( 97): Camera does not support setVideoSize()
E/CameraHardwareSec( 97): Non-metadata buffer mode is not supported!
W/StagefrightRecorder( 97): Failed to create the encoder
D/CameraSource( 97): reset: E
W/CameraService( 97): attempt to use a locked camera from a different process (old pid 97, new pid 2240)
D/CameraSource( 97): reset: X
E/MediaRecorder( 2240): start failed: -2147483648
E/videocamera( 2240): Could not start media recorder.
E/videocamera( 2240): java.lang.RuntimeException: start failed.
E/videocamera( 2240): at android.media.MediaRecorder.start(Native Method)
E/videocamera( 2240): at com.android.camera.VideoCamera.startVideoRecording(VideoCamera.java:1484)
E/videocamera( 2240): at com.android.camera.VideoCamera.onShutterButtonClick(VideoCamera.java:614)
E/videocamera( 2240): at com.android.camera.ShutterButton.performClick(ShutterButton.java:108)
E/videocamera( 2240): at android.view.View$PerformClick.run(View.java:16966)
E/videocamera( 2240): at android.os.Handler.handleCallback(Handler.java:615)
E/videocamera( 2240): at android.os.Handler.dispatchMessage(Handler.java:92)
E/videocamera( 2240): at android.os.Looper.loop(Looper.java:137)
E/videocamera( 2240): at android.app.ActivityThread.main(ActivityThread.java:4745)
E/videocamera( 2240): at java.lang.reflect.Method.invokeNative(Native Method)
E/videocamera( 2240): at java.lang.reflect.Method.invoke(Method.java:511)
E/videocamera( 2240): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:786)
E/videocamera( 2240): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:553)
E/videocamera( 2240): at dalvik.system.NativeStart.main(Native Method)
V/videocamera( 2240): Releasing media recorder.
V/videocamera( 2240): Empty video file deleted: /mnt/sdcard/DCIM/Camera/VID_20120710_025327.mp4.tmp
This is suggestive of a problem with the video encoding or camera HAL, but replacing libstagefrighthw.so with one built from the Jelly Bean device/samsung/crespo tree doesn't make a difference, and building camera.herring.so from that tree completely breaks the camera app (segfault in a call to libc from camera.herring.so).
There's a thinko in /init.herring.rc which means the tweak to the ondemand CPU governor isn't actually applied.
Lots of reports of Google Now and/or Google Search crashing. A logcat would be helpful for anyone trying to diagnose the problem.
Other notes:
Any ICS kernel should work with this Jelly Bean ROM. People have reported a variety problems with custom kernels. Please make sure you're using the stock kernel before reporting bugs.
That said, it appears that the official release will use a different wireless driver (the bcmdhd driver which Galaxy Nexus already uses), so ICS kernel releases may need some changing for Jelly Bean.
If you're having problems with Market or something else crashing, please provide a logcat -- otherwise problems are difficult to diagnose. Make sure you've wiped all data if you're flashing over an existing ICS installation.
There will be an SP2 to fix the governor issue, along with any other easy wins that crop up, but I'd gently suggest that most further effort should be devoted to a build from source.
figured it out followed this to get past the setup screen:
http://www.youtube.com/watch?v=L5XjF6sPef4
Uploading a version of the port zipaligned and deoxeded... All fixed...
Regards,
Urko
urko95 said:
Uploading a version of the port zipaligned and deoxeded... All fixed...
Regards,
Urko
Click to expand...
Click to collapse
urko what u mean all fixed ??
urko95 said:
Uploading a version of the port zipaligned and deoxeded... All fixed...
Regards,
Urko
Click to expand...
Click to collapse
Can you explain more?
legolas93 said:
Can you explain more?
Click to expand...
Click to collapse
Sorry, I mean that all fixes are applyed, the fixes that Steve realased!
EDIT: Uploading it right now
Regards,
Urko
why is the "ro.build.type" in sp1 still "eng" in stead of "user"?
Hello steven i flashed this port this morning... working very smooth . One problem i have which I'd like to solve. When trying to restore to 4.0.4 cyber or m6 i got md5 mismatch
.. any way i could restore them ? Thank you
Sent from my Nexus S using xda app-developers app
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.
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 ?
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
Hello everyone!
I installed Xposed on Moto G4 Android 7.1.2 (Nougat) into which I had installed e foundation custom ROM (bravo to me!). I wanted to install XPrivacyLua.
I downloaded the Xposed Framework v90-beta3 via Magisk. This resulted in a message in yellow: "Xposed Framework version 89 is installed, but not active. Please check the logs for details." "Could not load available ZIP files. Pull down to try again".
Please help! I would greatly appreciate your help, as I am a complete beginner. Actually, believe it or not, I haven't even used a smartphone before (true). I thought I would start on the right foot by installing a custom ROM, and going in the deep end. So far so good. But I need help and guidance from experienced folks now!
How can I make the Xposed active?
In Magisk, it says Xposed Framework v90-beta3 by rovo89 is installed. So not sure if I have v89 or v90 installed.
I have also given root access to Xposed in Magisk.
XPrivacyLua has also been installed, but it's not active, since Xposed is still inactive.
LOGS say as follows:
10-20 13:26:12.712 I/Xposed ( 457): ..............................
10-20 13:26:12.712 I/Xposed ( 457): Starting Xposed version 89, compiled for SDK 25
10-20 13:26:12.712 I/Xposed ( 457): Device: Moto G4 (Motorola), Android version 7.1.2 (SDK25)
10-20 13:26:12.712 I/Xposed ( 457): ROM: e_athene-userdebug 7.1.2 NJH47F 20210531 dev-keys,dev-release
10-20 13:26:12.712 I/Xposed ( 457): Build fingerprint: motorola/athene/athene:7.0/NPJ25.93-14/16:user/release-keys
10-20 13:26:12.712 I/Xposed ( 457): Platform: armeabi-v7a, 32-bit binary, system server: yes
10-20 13:26:12.712 I/Xposed ( 457): SELinux enabled: yes, enforcing: yes
10-20 13:26:13.754 I/Xposed ( 457): ................................
10-20 13:26:13.754 I/Xposed ( 457): ERROR: Could not access Xposed jar '/system/framework/XposedBridge.jar'
read: unexpected EOF!
Please advise re above log: "ERROR: Could not access Xposed jar '/system/framework/XposedBridge.jar'read: unexpected EOF!" How can I let Xposed access the Xposed jar?
I have found a similar problem on: https://github.com/rovo89/XposedBridge/issues/200
People in above GitHub page talked about solving the problem by giving permission by using a root explorer. I am not sure what a root explorer is and how to use it, and whether using it would solve the situation?
I wonder if someone can please explain in simple language?
I am awaiting with great anticipation your voice of experience, everyone!
Hi everyone,
I wonder if you had a chance to muse over the above situation?
Please do help. I am counting on you all.
Thank you in advance!
Yours
CD
Hi everyone? No one around? Where are the experienced guys you hear of on XDA....?
Please help.
Try using original xposed for your device for android 7. I never had much luck using magisk version
Dear spawnlives,
Thank you so much for your reply. I am very grateful for your generous help.
I have a feeling I have already tried the original xposed without success, as I tried so many things.
But will definitely try it again!
All best wishes,
CD
Hello spawnlives and everyone,
Following your kind suggestion, spawnlives, I looked through my notes. I had tried the original Xposed for Android 7, which I had downloaded from XDA site.
The result was that Xposed didn't even show up in apps list, for some reason. It was nowhere to be seen - not even an icon.
So if you have further ideas, I would be most appreciative.
Unfortunately, the ROM I'm using had an update 2 days ago, which made Magisk to stop working. So Xposed has turned from yellow warning to red...
Sadly I don't think I can sort everything out until beginning of Dec, due to work.
I'll be back.
All best wishes,
CD
countessdracula said:
Hello spawnlives and everyone,
Following your kind suggestion, spawnlives, I looked through my notes. I had tried the original Xposed for Android 7, which I had downloaded from XDA site.
The result was that Xposed didn't even show up in apps list, for some reason. It was nowhere to be seen - not even an icon.
So if you have further ideas, I would be most appreciative.
Unfortunately, the ROM I'm using had an update 2 days ago, which made Magisk to stop working. So Xposed has turned from yellow warning to red...
Sadly I don't think I can sort everything out until beginning of Dec, due to work.
I'll be back.
All best wishes,
CD
Click to expand...
Click to collapse
Bear in mind, much like magisk. xposed has two components to it.
Framework and installer ( control ) app
The framework will not show up in the system an app, only the installer ( control ) app will.
If you are going to use rovo's version you will have to use his installer app as well.