Database Info

[Resurrected][MOD] LG Cam V3.0 for OTA Based Roms [ (10/28/11)]

Bounty Link:
Use this to Donate to the Project Itself for all of those involved in the hardwork Jface,Doniqq, and myself
Bugs List (Last updated 9/5/11)
Code:
-FFC Squished on some versions
-FFC roatated 90 Degrees CW on V1.5 & Up
-FFC @ Full Res Video still shows green boxes (missing libs?)
Update (9/5/11): LG Cam V3.0 -Major Fixes in this one
Testing now... if all goes well expect update package shortly. 2:42AM EST
Stitch Shot: Confirmed working
Panorama Shot: Confirmed Working
Continuous Shot: Confirmed Working
Zoom while recording Video in all modes : Confirmed working
Touch to focus : Confirmed Working
Taking Pictures in portrait flipped : Confirmed working
Recording at 1080P @ 24 FPS / 720P @ 30 FPS : Confirmed Working
Download LG Cam V3.0: Here
Update (8/5/11): LGCam V1.5 - Fxied for Real This Time - for the trolls i mean the update package
Download LGCam V1.5: Here
THIS WILL NOT WORK ON CM7 OR ANYTHING BASED ON CM7/AOSP FOR NOW
Restore AOSP/OTA GB Cam
V1.4
Don't want to talk about it
Code:
V1.5 Updates:
-Fixed ZIP Package, now flashable, I promise (Damn Signtool replaced the com folder :/) :o
-Fixed 1080P @ 24FPS/30 FPS same as stock FROYO
-Fixed Zoom while recording Video
- Stock Cam Icon
- Still needs to fix FFC
-Enjoy, Report any bugs in the thread
-Donate and help me buy a bottle of Belevedere Black:)
V1.4
Burning in hell somewhere
Click to expand...
Click to collapse

flak0 said:
Hey Devs and ofcourse Doniqq first off amazing work on EB i love it. Im using the FR version. Ok so basically I am posting this thread because I figured out for sure why the LG Camera will not work on GB. It is not a lack of drivers like everyone has said. Basically when the Camera.Apk(LG Camera) is launched it looks for Libamce.so (i figured this out by reverse engineering the LG Camera and found the referrence on where it looks for the shared library libamce.so.) I went ahead and tried to push the LG Camera with the libamce.so yet still got a force close, this time the error was a reloc lbrary error looking for a _NZCamera6Connect function. I then went ahead an decompiled the libamce.so and found that it depends on libnvomx.so, then I decompiled libnvomx.so and found that it depends on libm.so, then I tried pushing all three libs to GB and still got a force close. After digging deep enough I found that libm.so depends on libcamera_client.so which I also decompiled and then I found the _NZCamera6Connect fuction is contained here. I attempted to push the libcamera_cleint.so to to GB and boot failed, then I tried editing the update-zip file to include the libcamera_client.so (From Froyo) and boot also failed. I am positive that once we get this libcamera_client.so ported from FROYO to GB the LG Camera will work. Luckily there is no dependency on the framework. This is where I need your help since I know your the dev who made EB possible or any Dev thats out there Faux, Morific Thanks.
Here is the header of the decompiled libamce.so just in case:
Click to expand...
Click to collapse
I'm no dev, but I just want to thank you for continuing to try and bring the LG cam to Gingerbread. Hopefully a dev will gladly help you out with this issue. Once again thank you for taking the time to try and get this hard headed app to work.
Sent from my LG-P999 using XDA Premium App

[depricated as of 9/5/11 - history of lgcam on gb]
Update (8/3/11): LG CAM for CM7 removed until fixed. Too many people were flashing on MIUI and CM7 Based ROMS
New Version for Stock OTA based ROMS coming out tonight.
Proposed fixes include -> 24/30 FPS @ 1080P and Zoom while video recording
Also moved some of the original OP two posts down to clean up the OP.
Update(8/2/11): LG Cam for CM 7 Beta
Below is what you have all been asking for, it is a beta of LG Cam for CM7. If you are willing to take the risk go ahead and flash BUT FIRST MAKE SURE YOU NANDROID. I have also attached CM7 Cam again if it fails to work and/or if you wish to go back. Please update the thread with any errors, logcats preferred.
Edit: Update(8/2/11 @ 4:42AM EST) below.
I was able to Port the LGE folder from GB to CM7 into the framework successfully however now when I open the CAM I am getting a null pointer exception. Anyone willing to help here please.
Code:
I/ActivityManager( 1074): Starting: Intent { act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10200000 cmp=com.android.camera/.ArcCamera } from pid 1279
I/ActivityManager( 1074): Start proc com.android.camera for activity com.android.camera/.ArcCamera: pid=3750 uid=10034 gids={1006, 1015}
D/ ( 984): NVRM_DAEMON(819): rt_exist=2, add client ref
D/ ( 984): set continue (1280x960)
D/ ( 984): set continue (1280x1024)
D/ ( 984): set continue (1280x1024)
D/ ( 984): set continue (1360x768)
D/ ( 984): set continue (1440x900)
D/ ( 984): set continue (1680x1050)
D/ ( 984): set BetterMode (1280x720)
D/ ( 984): set BetterMode (1920x1080)
D/ ( 984): set BetterMode (1280x720)
D/ ( 984): set BetterMode (1920x1080)
D/ ( 984): set BetterMode (1920x1080)
D/ ( 984): set BetterMode (1920x1080)
D/ ( 984): set BetterMode (1920x1080)
I/WindowManager( 1074): Setting rotation to 1, animFlags=1
I/ActivityManager( 1074): Config changed: { scale=1.0 imsi=310/260 loc=en_US touch=3 keys=1/1/2 nav=1/1 orien=2 layout=34 uiMode=17 seq=7 themeResource=null}
I/PowerWidget( 1243): Clearing any old widget stuffs
I/PowerWidget( 1243): Setting up widget
I/PowerWidget( 1243): Default buttons being loaded
I/PowerWidget( 1243): Button list: toggleWifi|toggleBluetooth|toggleGPS|toggleSound
I/PowerWidget( 1243): Setting up button: toggleWifi
I/PowerWidget( 1243): Setting up button: toggleBluetooth
I/PowerWidget( 1243): Setting up button: toggleGPS
I/PowerWidget( 1243): Setting up button: toggleSound
D/szipinf ( 3750): Initializing inflate state
I/===ArcCamera=== 1.1.0.1( 3750): Performance log:Load so2011-08-02 08:36:10.376 cost:6ms
I/===ArcCamera=== 1.1.0.1( 3750): Performance log:Launch camera
[color="blue"][size="4"]major update 7/28/11[/size]
[/color]
working lg cam on 2.3.3 ota & xborders stock rom (huge thanks to jumaaneface) once the cam is confirmed working on cm7 & aosp the bounty will be paid. I will also be looking into the actual cam app by decompiling source to see if we can fix the 1080p recording to make it record at 30 fps.
Again thanks to all the supporters and to jumaaneface who made this possible.
:d hey devs and ofcourse doniqq first off amazing work on eb i love it. Im using the fr version. Ok so basically i am posting this thread because i figured out for sure why the lg camera will not work on gb. It is not a lack of drivers like everyone has said. Basically when the camera.apk(lg camera) is launched it looks for libamce.so (i figured this out by reverse engineering the lg camera and found the referrence on where it looks for the shared library libamce.so.) i went ahead and tried to push the lg camera with the libamce.so yet still got a force close, this time the error was a reloc lbrary error looking for a [b]_nzcamera6connect[/b] function. I then went ahead an decompiled the libamce.so and found that it depends on libnvomx.so, then i decompiled libnvomx.so and found that it depends on libm.so, then i tried pushing all three libs to gb and still got a force close. After digging deep enough i found that libm.so depends on libcamera_client.so which i also decompiled and then i found the [b]_nzcamera6connect[/b] fuction is contained here. I attempted to push the libcamera_cleint.so to to gb and boot failed, then i tried editing the update-zip file to include the libcamera_client.so (from froyo) and boot also failed. I am positive that once we get this libcamera_client.so ported from froyo to gb the lg camera will work. Luckily there is no dependency on the framework. This is where i need your help since i know your the dev who made eb possible or any dev thats out there faux, morific thanks.
[b]update(7/27/11): Bounty increased to $100.00 thanks to:
[quote]eleeo037037 :$10
adevilfish :$10
bakedpatato : $5.00[/quote][/b]
[b]major update (7/26/11)
since the ota is official and the lg cam is not contained i am starting a bounty at $75.00 for the first person who can figure this out. I have tried numerous attempts using different approaches to no avail. There are others in the thread who mentioned they will also put up a bounty. I alone will pay $75.00 plus whatever anyone else decides to throw in the pot. [/b]
[b]update 3 (7/22/11): Attempted again to change some files in the framework and upon boot logcat threw error for missing decl from the camera$files in the framework. I pushed the libcamera_client.so from froyo and then the messaged changed to this:
[quote]i//system/xbin/busybox( 1015): Sysctl: /etc/sysctl.conf: No such file or directory
i//system/xbin/busybox( 1015): -k: No such file or directory
i//system/xbin/busybox( 1015): [: 61m: Bad number[/b][/quote]
[b]update 2(7/22/11) : Flashing eb 1.0.5 gr v21e rom with modified framework and it failed, so i pushed libcamera_client.so and it failed, error below [/b]
[quote]- waiting for device -
--------- beginning of /dev/log/main
i/netd ( 1018): Netd 1.0 starting
--------- beginning of /dev/log/system
i/vold ( 1017): Vold 2.1 (the revenge) firing up
d/vold ( 1017): Usb_configuration switch is not enabled in the kernel
d/vold ( 1017): Volume extsdcard state changing -1 (initializing) -> 0 (no-media)
d/vold ( 1017): Volume sdcard state changing -1 (initializing) -> 0 (no-media)
d/vold ( 1017): Volume extsdcard state changing 0 (no-media) -> 1 (idle-unmounted)
w/vold ( 1017): Duplicate state (1)
d/vold ( 1017): Volume sdcard state changing 0 (no-media) -> 1 (idle-unmounted)
w/vold ( 1017): Duplicate state (1)
w/vold ( 1017): Duplicate state (1)
i/debug ( 1019): Debuggerd: Jul 15 2011 10:15:43
d/ ( 1029): Open is ok, now, we are in user_land!
D/ ( 1029): Set continue (1280x960)
d/ ( 1029): Set continue (1280x1024)
d/ ( 1029): Set continue (1280x1024)
d/ ( 1029): Set continue (1360x768)
d/ ( 1029): Set continue (1440x900)
d/ ( 1029): Set continue (1680x1050)
d/ ( 1029): Set bettermode (1280x720)
d/ ( 1029): Set bettermode (1920x1080)
d/ ( 1029): Set bettermode (1280x720)
d/ ( 1029): Set bettermode (1920x1080)
d/ ( 1029): Set bettermode (1920x1080)
d/ ( 1029): Set bettermode (1920x1080)
d/ ( 1029): Set bettermode (1920x1080)
d/kipc ( 1020): Kipc_init()
d/kipc ( 1020): Address is 127.0.0.1, port is 45211
d/kipc ( 1020): Binding...
D/kipc ( 1020): Listening...
D/kipc ( 1020): Accepting...
D/ganril ( 1020): Gan ril starting
d/ganril ( 1020): Entering main loop
d/ganat ( 1020): 65 6e 74 65 72 69 6e 67 20 6d 61 69 6e 4c 6f 6f
d/ganat ( 1020): 70 28 29
d/ganat ( 1020): Gan_at_open
d/ganpsat ( 1020): Gan_ps_at_open
d/ganat ( 1020): Additional logging enabled. Going to call readline()
d/ganat ( 1020): Readline
d/ganat ( 1020): Readline : Before read
i/ ( 1030): Screencaptured accept lsocket: 9
i/vold ( 1017): Usb_mass_storage function disabled
e/netlinkevent( 1017): Netlinkevent::findparam(): Parameter 'switch_name' not found
e/netlinkevent( 1017): Netlinkevent::findparam(): Parameter 'switch_state' not found
w/vold ( 1017): Switch /devices/virtual/switch/usb_mass_storage event missing name/state info
i/rescuestarter( 1026): Rescuestarter 6.3.274 starts
i/rescuestarter( 1026): Ready, waiting for connection
e/netlinkevent( 1017): Netlinkevent::findparam(): Parameter 'switch_name' not found
e/netlinkevent( 1017): Netlinkevent::findparam(): Parameter 'switch_state' not found
w/vold ( 1017): Switch /devices/virtual/switch/usb_mass_storage event missing name/state info
i//system/xbin/busybox( 1015): Sysctl: /etc/sysctl.conf: No such file or directory
i//system/xbin/busybox( 1015): -k: No such file or directory
i//system/xbin/busybox( 1015): [: 61m: Bad number
i/vold ( 1017): Usb_mass_storage function enabled
d/vold ( 1017): Share method ums now available
i//system/xbin/busybox( 1015): Mount: Invalid argument
i//system/xbin/busybox( 1015): Run-parts: /system/etc/init.d/10ext4tuneup exited with code 255
i//system/xbin/busybox( 1015): Starting automatic zipalign 07-22-2011 22:21:12
i//system/xbin/busybox( 1015): Zipalign: Not found
i//system/xbin/busybox( 1015): Zipalign already completed on /data/app/*.apk
i//system/xbin/busybox( 1015): Zipalign: Not found
i//system/xbin/busybox( 1015): Zipalign already completed on /system/app/accountandsyncsettings.apk
i//system/xbin/busybox( 1015): Zipalign: Not found
i//system/xbin/busybox( 1015): Zipalign already completed on /system/app/applicationsprovider.apk
i//system/xbin/busybox( 1015): Zipalign: Not found
i//system/xbin/busybox( 1015): Zipalign already completed on /system/app/bluetoothopp.apk
i//system/xbin/busybox( 1015): Zipalign: Not found
i//system/xbin/busybox( 1015): Zipalign already completed on /system/app/bluetoothpbap.apk
i//system/xbin/busybox( 1015): Zipalign: Not found[/quote]
[b]update 7/22/11 - working on patching and porting elements from the froyo framework to gb[/b]
[img]http://forum.xda-developers.com/attachment.php?attachmentid=662618&stc=1&d=1311355083[/img]
[b](7/21/11)major update: Lg releases stock gb rom v21e however lg cam is not on board. This thread will.continue until we can successfully port the lg cam to gb. [/b]
[b]update 7/20/2011:
[quote]status update: Spoke with doniqq via pm he is working hard for us (so please thank him) to port the lg cam from froyo to gb. I am going to take another stab at this tonight and check 1 more thing. For those that had/have the nexus 1, i was the one who successfully ported the cm camera to rodriguez miui when everyone thought it was impossible. I am pretty sure the framework.jar is not part of this however when i moved the cm 7 cam to miui i did modify the framework, so i will take a look at this tonight before ruling it out completely.
[/quote][/b]
[b]here is the header of the decompiled libamce.so just in case:[/b]
[quote].plt:000459f4 ;
.plt:000459f4 ; +-------------------------------------------------------------------------+
.plt:000459f4 ; | this file has been generated by the interactive disassembler (ida) |
.plt:000459f4 ; | copyright (c) 2009 by hex-rays, |
.plt:000459f4 ; | license info: B3-ada1-9d85-df |
.plt:000459f4 ; | licensed user |
.plt:000459f4 ; +-------------------------------------------------------------------------+
.plt:000459f4 ;
.plt:000459f4 ; input md5 : 2ebb5ff4c8e8cf34c40ffc3aed9e8042
.plt:000459f4
.plt:000459f4 ; ---------------------------------------------------------------------------
.plt:000459f4 ; file name : C:\users\flak0-hpn3\downloads\libamce.so
.plt:000459f4 ; format : Elf (shared object)
.plt:000459f4 ; imagebase : 8000
.plt:000459f4 ; needed library 'libcamera_client.so'
.plt:000459f4 ; needed library 'libsurfaceflinger_client.so'
.plt:000459f4 ; needed library 'libui.so'
.plt:000459f4 ; needed library 'liblog.so'
.plt:000459f4 ; needed library 'libcutils.so'
.plt:000459f4 ; needed library 'libutils.so'
.plt:000459f4 ; needed library 'libhardware.so'
.plt:000459f4 ; needed library 'libmedia.so'
.plt:000459f4 ; needed library 'libandroid_runtime.so'
.plt:000459f4 ; needed library 'libc.so'
.plt:000459f4 ; needed library 'libm.so'
.plt:000459f4 ; needed library 'libstdc++.so'
.plt:000459f4 ; needed library 'libdl.so'
.plt:000459f4 ; needed library 'libbinder.so'
.plt:000459f4 ; needed library 'libskia.so'
.plt:000459f4 ; needed library 'libicuuc.so'
.plt:000459f4 ; needed library 'libegl.so'
.plt:000459f4 ; needed library 'libnvomx.so'
.plt:000459f4 ;
.plt:000459f4 ; eabi version: 5
.plt:000459f4 ;
.plt:000459f4
[/quote][/quote]
Click to expand...
Click to collapse

anybody try contacting faux or morfic to see if they could take a look? They are both very cool guys. I can talk to them if you want.

I have a silly question? If you use titanium back up and restore the LG camera would that work? If not, why?

I contacted both of them plus numerous devs.
jdkackley said:
anybody try contacting faux or morfic to see if they could take a look? They are both very cool guys. I can talk to them if you want.
Click to expand...
Click to collapse
Sent from my LG-P999 using XDA App

ClausMontoya said:
I have a silly question? If you use titanium back up and restore the LG camera would that work? If not, why?
Click to expand...
Click to collapse
I know it wont work but I couldnt tell you why. I thought the same thing and have tried it.

bls2633 said:
I know it wont work but I couldnt tell you why. I thought the same thing and have tried it.
Click to expand...
Click to collapse
Doesn't Titanimum just back up the apk file and not the compiled shared object?
Even so it'd be scary to think that it would somehow overwrite shared objects, potentially breaking the OS.

ClausMontoya said:
I have a silly question? If you use titanium back up and restore the LG camera would that work? If not, why?
Click to expand...
Click to collapse
I believe that what has been explained above is that there are libraries that the apk depend on to function that are not available on CM7 at the moment. (I could be wrong though)

yeah it's a similar reason if you backup DSP Manager from CM7 and try to install it on stock it will basically do nothing.

hey everyone i am still waiting for some devs to respond. Doniqq said he would take a look and let me know. We are 90% to having the LG Cam on GB.
If anyone else is good with shared objects in Android let me know.

Can you post the libcamera_client.so decompiled?
In theory this should be fairly simple to compile under gingerbread.

Scyth3 said:
Can you post the libcamera_client.so decompiled?
In theory this should be fairly simple to compile under gingerbread.
Click to expand...
Click to collapse
I can post it but i don't think it will compile, Remember i used a deconplier to reveal the source.
Sent from my LG-P999 using XDA App

I'll join in on this when I get home later. Has anyone tried contacting LG? They seem pretty reasonable.

Nah he means like talking to them about the camera drivers and what not I'm sure he wont say he'd trying to convert there froyo camera app to work with gingerbread lol they should be pretty reasonable

Yeah that's what I meant. I figure if there's something we need they might be able to help us. OP PM me

Status Update: 7/20/2011 US EST
Status Update: Spoke with Doniqq via PM he is working hard for us (so please thank him) to port the LG Cam from Froyo to GB. I am going to take another stab at this tonight and check 1 more thing. For those that had/have the Nexus 1, I was the one who successfully ported the CM Camera to Rodriguez MIUI when everyone thought it was impossible. I am pretty sure the framework.jar is not part of this however when I moved the CM 7 cam to MIUI I did modify the framework, so I will take a look at this tonight before ruling it out completely.

Thank u everyone, your thank yous motivate that much more. I will keep u updated.
Sent from my LG-P999 using XDA App

Its solved because i believe the reason why the LG cam won't work has been found and the culprit is the libcamera_client.so from Froyo to GingerBread. Its now requires the work of a dev to port. Just saying
Sent from my LG-P999 using XDA App

Thanks to Chuckhriczko who is also jumping on board to help.
Faux responded and respectfully informed me that he is working on several projects however if he has some spare time he will take a look for us.
Sent from my LG-P999 using XDA App

aosp kitkat4.4 nexus 7(deb) not boot

hi all:
i download aosp kitkat4.4 source codes from google website. i compiled the code. i got the ROM.but when i flash the ROM to my device nexus 7(deb). it cannot boot.
from the log. i found that following error log. the sentence "couldn't find an OpenGL ES implementation" maybe cause the fatal question.
any advices is welcomed !
thank
brian
02-10 08:37:07.375: E/QCOMKeyMaster(17633): failed to load qseecom library
02-10 08:37:07.375: E/keystore(17633): could not open keymaster device in keystore (Operation not permitted)
02-10 08:37:07.375: E/keystore(17633): keystore keymaster could not be initialized; exiting
02-10 08:37:07.405: A/libEGL(17630): couldn't find an OpenGL ES implementation
02-10 08:37:07.405: A/libc(17630): Fatal signal 6 (SIGABRT) at 0x000044de (code=-6), thread 17630 (surfaceflinger)
02-10 08:37:07.575: E/msm8960_platform(17632): platform_init: DLOPEN failed for libacdbloader.so
02-10 08:37:07.575: E/msm8960_platform(17632): platform_init: DLOPEN failed for libcsd-client.so
02-10 08:37:07.575: E/MonoPipe(17632): Failed to fetch local time frequency when constructing a MonoPipe (res = -32). getNextWriteTimestamp calls will be non-functional

Android L Discussion (CM12/AOSP/all other builds...)

Hi,
First of all looks like there isn't anyone started building Android Lollipop for i9500
So lets make this thread for discussing about all Lollipop ROMS
I wanted to say, i built for i9500 already
There are bugs
If i can see anything on screen, probably it will be the lockscreen.
AOSP Lollipop Recovery (recovery.img) - OK!
AOSP Lollipop Kernel+ramdisk (boot.img) - OK!
AOSP Lollipop System - [PVRSRV PROBLEM : PVRSRVBridgeCall: Failed to access device. Function ID:3223086848 (Bad address)]
Probably something related about including vendor files on build(because of AOSP)
doesn't load graphics/display driver
E/IMGSRV ( 3929): :0: PVRSRVBridgeCall: Failed to access device. Function ID:3223086848 (Bad address).
E/IMGSRV ( 3929): :0: PVRSRVEnumerateDevices: BridgeCall failed
E/IMGSRV ( 3929): :0: PVRSRVConnect: Unable to enumerate devices.
E/IMGSRV ( 3929): :0: Couldn't connect to services
E/dex2oat ( 2811): Failed to open writable oat file /data/dalvik-cache/arm/[email protected]@boot.oat for /data/dalvik-cache/arm/[email protected]@boot.oat: File size of 0 bytes not large enough to contain ELF header of 52 bytes: '/data/dalvik-cache/arm/[email protected]@boot.oat'
E/dex2oat ( 2811): Failed to create image file /data/dalvik-cache/arm/[email protected]@boot.art
E/IMGSRV ( 3929): :0: PVRSRVBridgeCall: Failed to access device. Function ID:3223086848 (Bad address).
E/IMGSRV ( 3929): :0: PVRSRVEnumerateDevices: BridgeCall failed
E/IMGSRV ( 3929): :0: PVRSRVConnect: Unable to enumerate devices.
E/IMGSRV ( 3929): :0: OpenPVRServices: Failed to open services connection
E/IMGSRV ( 3929): :0: hal_init: Failed to open services (err=-14)
E/IMGSRV ( 3929): :0: hal_open: Graphics HAL not initialized
E/IMGSRV ( 3929): :0: hal_open: Graphics HAL not initialized
E/hwcomposer( 3929): failed to open gralloc
E/SurfaceFlinger( 3929): composer device failed to initialize (Invalid argument)
E/SurfaceFlinger( 3929): ERROR: failed to open framebuffer (Not a typewriter), aborting
F/libc ( 3929): Fatal signal 6 (SIGABRT), code -6 in tid 3929 (surfaceflinger)
@intervigilium @Alberto96 @alvin14

doga.ozkaraca said:
Hi,
First of all looks like there isn't anyone started building Android Lollipop for i9500
So lets make this thread for discussing about all Lollipop ROMS
I wanted to say, i built for i9500 already
There are bugs
If i can see anything on screen, probably it will be the lockscreen.
AOSP Lollipop Recovery (recovery.img) - OK!
AOSP Lollipop Kernel+ramdisk (boot.img) - OK!
AOSP Lollipop System - [PVRSRV PROBLEM : PVRSRVBridgeCall: Failed to access device. Function ID:3223086848 (Bad address)]
Probably something related about including vendor files on build(because of AOSP)
doesn't load graphics/display driver
E/IMGSRV ( 3929): :0: PVRSRVBridgeCall: Failed to access device. Function ID:3223086848 (Bad address).
E/IMGSRV ( 3929): :0: PVRSRVEnumerateDevices: BridgeCall failed
E/IMGSRV ( 3929): :0: PVRSRVConnect: Unable to enumerate devices.
E/IMGSRV ( 3929): :0: Couldn't connect to services
E/dex2oat ( 2811): Failed to open writable oat file /data/dalvik-cache/arm/[email protected]@boot.oat for /data/dalvik-cache/arm/[email protected]@boot.oat: File size of 0 bytes not large enough to contain ELF header of 52 bytes: '/data/dalvik-cache/arm/[email protected]@boot.oat'
E/dex2oat ( 2811): Failed to create image file /data/dalvik-cache/arm/[email protected]@boot.art
E/IMGSRV ( 3929): :0: PVRSRVBridgeCall: Failed to access device. Function ID:3223086848 (Bad address).
E/IMGSRV ( 3929): :0: PVRSRVEnumerateDevices: BridgeCall failed
E/IMGSRV ( 3929): :0: PVRSRVConnect: Unable to enumerate devices.
E/IMGSRV ( 3929): :0: OpenPVRServices: Failed to open services connection
E/IMGSRV ( 3929): :0: hal_init: Failed to open services (err=-14)
E/IMGSRV ( 3929): :0: hal_open: Graphics HAL not initialized
E/IMGSRV ( 3929): :0: hal_open: Graphics HAL not initialized
E/hwcomposer( 3929): failed to open gralloc
E/SurfaceFlinger( 3929): composer device failed to initialize (Invalid argument)
E/SurfaceFlinger( 3929): ERROR: failed to open framebuffer (Not a typewriter), aborting
F/libc ( 3929): Fatal signal 6 (SIGABRT), code -6 in tid 3929 (surfaceflinger)
Click to expand...
Click to collapse
Maybe Alberto96 can help u?

I don't have time to work on a whole new android version. School is killing me.

Alberto96 said:
I don't have time to work on a whole new android version. School is killing me.
Click to expand...
Click to collapse
same.. :highfive:
i was sick and stayed home today, and that was my only free-time for building Android L
there should be a way to solve that :crying:

Thanks for all the effort that somehow have contributed or are contributing.
Does the issue at hand will be resolved only get if Samsung release the source code with the Lollipop? Or some work of developers already can fix (no need to be based on source code from Samsung)?

Too bad it's not 9505
Ill keep tabs on this tho. I'm mainly looking for a kernel+ramdisk for 5.0 on 9505 or similar S4s.

Maybe we can get some help from here or here ?
and it seems @BlaqueDroid is also trying to boot lollipop on i9500

@doga.ozkaraca long time man! You had disappeared from our forum for a very long time! Good to see you man!
As @Arch9 said, @BlaqueDroid needed help building it too! Maybe y'all can figure it out together!
Happy compiling ?
Sent from my GT-I9500 using Tapatalk

Hey man which kernel are u using to compile coz the CM one is throwing errors for
---------- Post added at 06:33 AM ---------- Previous post was at 06:31 AM ----------
rgshah3 said:
@doga.ozkaraca long time man! You had disappeared from our forum for a very long time! Good to see you man!
As @Arch9 said, @BlaqueDroid needed help building it too! Maybe y'all can figure it out together!
Happy compiling ?
Sent from my GT-I9500 using Tapatalk
Click to expand...
Click to collapse
Hey man which Kernel are u using coz i tried the CM 11 one and the damn thing keeps throwing errors. Plz link me with the github Url

https://twitter.com/Antares__One this guy is doing some great stuff for our phone! Follow him for more updates #ThumbsUp

tkruijer said:
https://twitter.com/Antares__One this guy is doing some great stuff for our phone! Follow him for more updates #ThumbsUp
Click to expand...
Click to collapse
unfortunately it is for the I9505, I think the problem we have is different to boot

Even @gekkehenkie11 can help! He has done a lot of stuff recently to improve CM on our device! Maybe he can help boot CM12 on our device
Sent from my GT-I9500 using Tapatalk

@doga.ozkaraca
Welcome back buddy
Check this post
http://forum.xda-developers.com/showthread.php?p=56752819
Sent from my GT-I9500 using Tapatalk

I'm just found someone already build 5.0 for odroidxu in here, does we can do something with that? i'm trying to port it to i9500 but the result is nothing (stuck at boot)

Re-port a port is not a gold way ...

feraay said:
Re-port a port is not a gold way ...
Click to expand...
Click to collapse
Wut? re-port a port? what do you mean?

When can we expect fully working Android 5.0 based ROM?

ncenter said:
When can we expect fully working Android 5.0 based ROM?
Click to expand...
Click to collapse
31st Feb 2015
Sent from my GT-I9500 using Tapatalk

Yep, but unoficcial clean Lollipop ROM I mean.

ncenter said:
When can we expect fully working Android 5.0 based ROM?
Click to expand...
Click to collapse
How about you build it. And let us know? I heard its easy.

|Tutorial| How to build and install the new NetHunter|Marshmallow 6.0.1|

Hi guys.
Hope you all had a good Christmas , today i have a tutorial for you.
I will show you how to build the new version of NetHunter and install it to your device(must be a supported device,,see the list below)
-Nexus 4 (mako)
-Nexus 5 (hammerhead)
-Nexus 6 (shamu)
-Nexus 7 2012 (nakasi) and 2013 (razor)
-Nexus 9 (volantis)
-Nexus 10 (mantaray)
-One Plus One (bacon)
For my build setup i have Kali Linux installed in vmware, you could use virtualbox also.
If you have it installed on your pc,,more power to you.
So the requirements are:
-Have Kali Linux in a vm or installed on your pc(you could do the same thing on ubuntu,,but for the sake of it i use kali)
-A rooted supported android device(for marshmallow you should root your device with supersu 2.64 , as of the day i write this tutorial it's the latest)
Please note: this tutorial will not show you how to install linux neither how to root your android device.
I tested on a nexus 5 (my phone) and i have the latest marshmallow 6.0.1 on it and device is rooted.
It's not very complicated, if you ever built android roms or aosp from source it's a lot easier, the Nethunter guys made a script that pretty much
does it all by itself.
First thing , we will make a folder to work in, name it the way you want , i will just call it nethunter:
mkdir ~/nethunter
Then change directory into the folder you created:
cd ~/nethunter
Once inside the folder type:
Code:
git clone https://github.com/offensive-security/gcc-arm-linux-gnueabihf-4.7
After that we are going to clone the repo of the new installer branch like so:
Code:
git clone https://github.com/offensive-security/kali-nethunter.git -b newinstaller-fj
What we just done will created a folder named AnyKernel2 so we are going to change directory into it:
cd ~/nethunter/kali-nethunter/AnyKernel2
Then we are ready to build:
python build.py -d hammerhead -m (the -d means the device you are building for in my case it's a nexus 5 codename hammerhead,,and the -m means
marshmallow)
Once it's done,,you will have a zip file into the AnyKernel2 folder, and this is what you are going to flash in recovery to install NetHunter to your device.
The new installer is using aroma so you will be able to choose what to install.
On the first page or so you will be asked to install a version of SuperSu older than the one i provided you , untick this boxs, you don't want this to install and replace the version of SuperSu you curently have(2.64 ++)
When aroma will install it's probable that it will stuck at 40% for a couple of minutes, don't worry, let it do his things,,but if you are stuck there for more than
lets say 10 minutes just force shudown your device by holding the power button down and reboot,,Kali NetHunter should have been installed correctly anyway.
Make sure that once you boot with your new KaliNethunter go into the Kali app and update the chroot.
Also inside the Kali app "Check app update" from time to time since when there is a new thing added/fixed in Github it's just a matter of updating the app to get the update,,as easy as that.
That's about it, if you have any question feel free to ask.
**Big thanks to Binkybear and Jmingov who provided me usefull info**

Nethunter - chroot fails to install Nexus 5 - Cm13 nightly
jonathanxx1 said:
Hi guys.
Hope you all had a good Christmas , today i have a tutorial for you.
I will show you how to build the new version of NetHunter and install it to your device(must be a supported device,,see the list below)
-Nexus 4 (mako)
-Nexus 5 (hammerhead)
-Nexus 6 (shamu)
-Nexus 7 2012 (nakasi) and 2013 (razor)
-Nexus 9 (volantis)
-Nexus 10 (mantaray)
-One Plus One (bacon)
For my build setup i have Kali Linux installed in vmware, you could use virtualbox also.
If you have it installed on your pc,,more power to you.
So the requirements are:
-Have Kali Linux in a vm or installed on your pc(you could do the same thing on ubuntu,,but for the sake of it i use kali)
-A rooted supported android device(for marshmallow you should root your device with supersu 2.64 , as of the day i write this tutorial it's the latest)
Please note: this tutorial will not show you how to install linux neither how to root your android device.
I tested on a nexus 5 (my phone) and i have the latest marshmallow 6.0.1 on it and device is rooted.
It's not very complicated, if you ever built android roms or aosp from source it's a lot easier, the Nethunter guys made a script that pretty much
does it all by itself.
First thing , we will make a folder to work in, name it the way you want , i will just call it nethunter:
mkdir ~/nethunter
Then change directory into the folder you created:
cd ~/nethunter
Once inside the folder type:
Code:
git clone https://github.com/offensive-security/gcc-arm-linux-gnueabihf-4.7
After that we are going to clone the repo of the new installer branch like so:
Code:
git clone https://github.com/offensive-security/kali-nethunter.git -b newinstaller-fj
What we just done will created a folder named AnyKernel2 so we are going to change directory into it:
cd ~/nethunter/kali-nethunter/AnyKernel2
Then we are ready to build:
python build.py -d hammerhead -m (the -d means the device you are building for in my case it's a nexus 5 codename hammerhead,,and the -m means
marshmallow)
Once it's done,,you will have a zip file into the AnyKernel2 folder, and this is what you are going to flash in recovery to install NetHunter to your device.
The new installer is using aroma so you will be able to choose what to install.
On the first page or so you will be asked to install a version of SuperSu older than the one i provided you , untick this boxs, you don't want this to install and replace the version of SuperSu you curently have(2.64 ++)
When aroma will install it's probable that it will stuck at 40% for a couple of minutes, don't worry, let it do his things,,but if you are stuck there for more than
lets say 10 minutes just force shudown your device by holding the power button down and reboot,,Kali NetHunter should have been installed correctly anyway.
Make sure that once you boot with your new KaliNethunter go into the Kali app and update the chroot.
Also inside the Kali app "Check app update" from time to time since when there is a new thing added/fixed in Github it's just a matter of updating the app to get the update,,as easy as that.
That's about it, if you have any question feel free to ask.
**Big thanks to Binkybear and Jmingov who provided me usefull info**
Click to expand...
Click to collapse
I have followed the above instructions and was able to build and install nethunter.
- However, nethunter does not detect the wlan0 (screenshot attached)
- Installing chroot fails (download method)
- With very little that I know, I thought this must be the selinux in enforcing mode.
- Therefore I tried it again in permissive mode and still couldnt make progress.
Logs from catlog indicating the failure installing chroot
01-03 01:04:40.232 D/su (24412): Finishing su operation for app [uid:10146, pkgName: com.offsec.nethunter]
01-03 01:04:40.235 D/su (24410): sending code
01-03 01:04:40.235 D/su (24410): child exited
01-03 01:04:40.237 I/SuControllerImpl( 976): Got change
01-03 01:04:40.237 D/su (24408): client exited 0
01-03 01:04:40.377 E/Shell Error 6803): tar: seek failure: Value too large for defined data type
01-03 01:04:40.446 D/CreateChroot( 6803): Error:
01-03 01:04:40.446 D/CreateChroot( 6803): java.lang.RuntimeException: java.lang.RuntimeException
01-03 01:04:40.446 D/CreateChroot( 6803): at com.offsec.nethunter.utils.ShellExecuter.RunAsRootWithException(ShellExecuter.java:101)
01-03 01:04:40.446 D/CreateChroot( 6803): at com.offsec.nethunter.ChrootManagerFragment$UnziptarTask.doInBackground(ChrootManagerFragment.java:716)
01-03 01:04:40.446 D/CreateChroot( 6803): at com.offsec.nethunter.ChrootManagerFragment$UnziptarTask.doInBackground(ChrootManagerFragment.java:677)
01-03 01:04:40.446 D/CreateChroot( 6803): at android.os.AsyncTask$2.call(AsyncTask.java:295)
01-03 01:04:40.446 D/CreateChroot( 6803): at java.util.concurrent.FutureTask.run(FutureTask.java:237)
01-03 01:04:40.446 D/CreateChroot( 6803): at android.os.AsyncTask$SerialExecutor$1.run(AsyncTask.java:234)
01-03 01:04:40.446 D/CreateChroot( 6803): at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1113)
01-03 01:04:40.446 D/CreateChroot( 6803): at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:588)
01-03 01:04:40.446 D/CreateChroot( 6803): at java.lang.Thread.run(Thread.java:818)
01-03 01:04:40.446 D/CreateChroot( 6803): Caused by: java.lang.RuntimeException
01-03 01:04:40.446 D/CreateChroot( 6803): at com.offsec.nethunter.utils.ShellExecuter.RunAsRootWithException(ShellExecuter.java:93)
01-03 01:04:40.446 D/CreateChroot( 6803): ... 8 more
Logs from install NH
3 Jan 2016 00:44:59 - New instalation log file: /storage/emulated/0/nh_install_20160103_124456.log
3 Jan 2016 00:45:06 - Starting download. Standby&
3 Jan 2016 00:54:02 - Chroot download completed: Total 620.0 MB.
3 Jan 2016 00:54:02 - Original SHA: 45AF3ED319E520B85693EDB2058A82B942F875A0C7F4729DD3E3EAE6F110C7D106A7423639A58C53247BE3E95BF977B2107877FDB0A77B6F7B06286E73E75151
3 Jan 2016 00:54:29 - Checking file integrity... MATCH
3 Jan 2016 00:54:29 - New SHA: 45AF3ED319E520B85693EDB2058A82B942F875A0C7F4729DD3E3EAE6F110C7D106A7423639A58C53247BE3E95BF977B2107877FDB0A77B6F7B06286E73E75151
3 Jan 2016 00:54:31 - Unzipping and untarring....
3 Jan 2016 00:54:31 - Uncompressing the Chroot& (~10 min)
3 Jan 2016 01:01:52 - Deploying the Chroot& (~510 min)
3 Jan 2016 01:04:40 - Error: java.lang.RuntimeException: java.lang.RuntimeException
3 Jan 2016 01:04:40 - CreateChroot >> Error: java.lang.RuntimeException: java.lang.RuntimeException
3 Jan 2016 01:15:19 - New instalation log file: /storage/emulated/0/nh_install_20160103_124456.log
Any help is appreciated.
Thanks,
[email protected]

From where do I to start for customise it for Galaxy S5 ?
I'm new in Rom cooking
---------- Post added at 06:59 PM ---------- Previous post was at 06:47 PM ----------
Hi friend
Would you please help me to start on customising nethunter for Galaxy S5
I'm new in Rom customisation..
Really confused..I don't know where to start

[APP][PATCH] SnoopSnitch OnePlus Compatibility Patch

After some trial and error, I have identified the reason why snoopsnitch isn't working.
The issue is related to the DIAG initialization code in the diag-helper binary.
I'm attaching a working patch and a compiled APK (PM me for the link or maybe a mod. can attach it. I have 10 post link restriction) for your convenience.
PS: the code specifically look for OnePlus manufacturer but it may work on other devices too (with the appropriate changes)
Code:
diff --git a/contrib/diag_helper/jni/diag-helper.c b/contrib/diag_helper/jni/diag-helper.c
index ddb7fcb1..c1b00a33 100644
--- a/contrib/diag_helper/jni/diag-helper.c
+++ b/contrib/diag_helper/jni/diag-helper.c
@@ -3,6 +3,7 @@
#include <sys/socket.h>
#include <sys/stat.h>
#include <sys/un.h>
+#include <sys/system_properties.h>
#include <android/log.h>
@@ -13,6 +14,7 @@
#include <stdlib.h>
#include <unistd.h>
#include <arpa/inet.h>
+#include <string.h>
#define BUF_SIZE 1000000
@@ -62,9 +64,15 @@ open_diag_dev(void)
int diag_fd = -1;
int rv = -1;
int olderrno;
+ bool op = false;
+ char man[PROP_VALUE_MAX + 1];
+
+ __system_property_get("ro.product.manufacturer", man);
logmsg(ANDROID_LOG_DEBUG, "opening diag device");
+ if (strcasecmp("oneplus", man) == 0) op = true;
+
diag_fd = open("/dev/diag", O_RDWR|O_CLOEXEC);
if (diag_fd < 0) {
logmsg(ANDROID_LOG_FATAL, "error opening diag device: %m");
@@ -74,6 +82,7 @@ open_diag_dev(void)
const unsigned long DIAG_IOCTL_SWITCH_LOGGING = 7;
const int MEMORY_DEVICE_MODE = 2;
+ const int mode_param[] = { MEMORY_DEVICE_MODE, -1, 0 };
struct diag_logging_mode_param_t stMode = {
MEMORY_DEVICE_MODE, 0, 1
};
@@ -84,7 +93,10 @@ open_diag_dev(void)
rv = ioctl(diag_fd, DIAG_IOCTL_SWITCH_LOGGING, MEMORY_DEVICE_MODE);
if (rv < 0) {
olderrno = errno;
- rv = ioctl(diag_fd, DIAG_IOCTL_SWITCH_LOGGING, (void *)&stMode);
+ if(op)
+ rv = ioctl(diag_fd, DIAG_IOCTL_SWITCH_LOGGING, (void *)&mode_param, sizeof(mode_param));
+ else
+ rv = ioctl(diag_fd, DIAG_IOCTL_SWITCH_LOGGING, (void *)&stMode);
}
if (rv < 0) {
Credits: SRLabs, original author repository: https://opensource.srlabs.de/projects/snoopsnitch
{Mod edit: Added apk on request of OP @h3ph4est7s}

thanks
I've been looking for this for a while, I sent you a pm
it works perfectly thanks

Hi,
Thanks for the apk! It's great to see it again running (especially initializing) on my device, love it! As I already wrote in another posting in another thread (sorry for the double post, but in this specific case it's OK I think), there are two things that need to be mentioned:
- the patch level checks do not work on my device, maybe this depends in the ROM I'm using (I'm on Havoc 3.8 / Android 10) - I'll have to check if it maybe works with another ROM.
- I currently cannot say if the detection of silent SMS and IMSI Catchers really is working since I've havent't had such events till now. Silent SMSes should appear from time to time IMO. IMSI catcher events are extremely rare in my experience, I used Snoop Snitch for about one year two or three years ago and got two of those events in the whole year: one in Germany, one in Canada.
Cheers
Zap

I am also facing the same DIAG_CHAR initializing issue. I used your snoopsnitch apk to test on my Oneplus 5, LOS16. The app started, but closed immediately. The backend service keep on restarted. My logcat shows as below.
12-11 13:16:12.186 9407 9407 E [email protected]: Could not get passthrough implementation for [email protected]::ICameraProvider/legacy/0.
12-11 13:16:12.198 9417 9417 I diag-helper: starting
12-11 13:16:12.198 9417 9417 I diag-helper: test mode invoked
12-11 13:16:12.198 9417 9417 D diag-helper: opening diag device
12-11 13:16:12.198 9417 9417 F diag-helper: error setting diag device logging mode: Bad address/Invalid argument
12-11 13:16:12.199 9417 9417 E diag-helper: error opening DIAG device
12-11 13:16:12.200 9261 9261 E msd-service: Terminating MsdService after shutting down due to an unexpected error
12-11 13:16:12.202 9261 9261 I opSnitchServic: System.exit called, status: 1
12-11 13:16:12.202 9261 9261 I AndroidRuntime: VM exiting with result code 1, cleanup skipped.
12-11 13:16:12.215 1359 9176 I ActivityManager: Process .SnoopSnitchService (pid 9261) has died: fore SVC
12-11 13:16:12.215 1359 9176 W ActivityManager: Scheduling restart of crashed service de.srlabs.snoopsnitch/.qdmon.MsdService in 1000ms
12-11 13:16:12.215 1359 1405 W libprocessgroup: kill(-9261, 9) failed: No such process
12-11 13:16:12.215 1359 1405 I libprocessgroup: Successfully killed process cgroup uid 10092 pid 9261 in 0ms
Click to expand...
Click to collapse
Any kind of help is appreciated.

Installed this Mod on my OP7T Pro, but it crashes at start. The unmodified version starts flawless, but did mit recognize root privileges (message at the bottom "snoopsnitch require root access..."). On clicking the start network test button it tells me "could not initialize the diag interface". I checked diag_char in system and it is enabled. No Idea whats wrong. Using Android 10 with latest stabile stock OS.

EinsteinXXL said:
Installed this Mod on my OP7T Pro, but it crashes at start. The unmodified version starts flawless, but did mit recognize root privileges (message at the bottom "snoopsnitch require root access..."). On clicking the start network test button it tells me "could not initialize the diag interface". I checked diag_char in system and it is enabled. No Idea whats wrong. Using Android 10 with latest stabile stock OS.
Click to expand...
Click to collapse
Same here with Oxygen OS 11 beta. The modded app crashes on start and the original app can't "initilize diag driver."

On my OP3T with Android 11 (Arrow OS) it works. Same again as before: Starting and initializing perfectly, but the patch level checks do not work.
The Problem seems to be device-/SOC - specific.

Hello and thank you so very much for this. I had been wanting to use it for s long time and finally came across your workaround. Unfortunately it didn't work for me. I originally installed through nethunter store but I uninstalled that and installed yours. I am running Jaguar OS on OP8T rooted with magisk. I created a logcat hoping that you'll be able to hero me get it going. I am attaching it here. Thank you!