Database Users

[CM7] #28 wildfire still drops calls after a few seconds

Hello,
What I did:
- format all partitions except SDCARD
- removed all hidden android directories on SDCARD, only Media, downloaded nightly and gapps-gb and my nandroid-backup were left.
- reset to factory settings
- wiped cache
- applied newest radio 13.55.55.24H_3.35.20.10
- rebooted
- installed nightly #28
- installed gapps-gb-20110307
- rebooted
- entered SIM code
- skipped login to google
- called my mailbox
Phone call still drops after a few seconds.
D/SurfaceFlinger( 172): About to give-up screen, flinger = 0x93778
I/DEBUG ( 113): *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
I/DEBUG ( 113): Build fingerprint: 'google/passion/passion:2.3.3/GRI40/102588:user/release-keys'
I/DEBUG ( 113): pid: 114, tid: 136 >>> /system/bin/rild <<<
I/DEBUG ( 113): signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 00000004
I/DEBUG ( 113): r0 100ffb2c r1 00000001 r2 000000ff r3 00000000
I/DEBUG ( 113): r4 00000000 r5 000000ff r6 afd41504 r7 100ffb2c
I/DEBUG ( 113): r8 ae604fe5 r9 00000000 10 00100000 fp 00000001
I/DEBUG ( 113): ip 80074820 sp 100ffa90 lr 80050abf pc afd18ca0 cpsr 20000030
I/DEBUG ( 113): #00 pc 00018ca0 /system/lib/libc.so (fread)
I/DEBUG ( 113): #01 pc 00050abc /system/lib/libhtc_ril.so (ril_func_screen_state_notified)
I/DEBUG ( 113): #02 pc 00032d18 /system/lib/libhtc_ril.so (ril_request_on_request)
I/DEBUG ( 113): #03 pc 00004348 /system/lib/libril.so
I/DEBUG ( 113): #04 pc 00004cf0 /system/lib/libril.so
I/DEBUG ( 113): #05 pc 00004d3e /system/lib/libril.so
I/DEBUG ( 113): #06 pc 00005344 /system/lib/libril.so (_Z14ril_event_loopv)
I/DEBUG ( 113): #07 pc 0000505a /system/lib/libril.so
I/DEBUG ( 113): #08 pc 00011cf4 /system/lib/libc.so (__thread_entry)
I/DEBUG ( 113): #09 pc 000118a4 /system/lib/libc.so (pthread_create)
I/DEBUG ( 113):
I/DEBUG ( 113): code around pc:
I/DEBUG ( 113): afd18c80 bd101c18 1c15b5f0 b0851c0a 4e4d436a
I/DEBUG ( 113): afd18c90 447e9103 92011c1c d1012a00 e08e2500
I/DEBUG ( 113): afd18ca0 2b00685b 2100da01 1c076061 078289a0
I/DEBUG ( 113): afd18cb0 6be2d572 d16f2a00 58734943 2e00681e
I/DEBUG ( 113): afd18cc0 f7ffd101 89a3fd9d 60602000 d474069a
I/DEBUG ( 113):
I/DEBUG ( 113): code around lr:
I/DEBUG ( 113): 80050a9c 2800efd2 4b6fd139 af1d4a6f 18a918e8
I/DEBUG ( 113): 80050aac e840f7c1 1c231c04 22ff2101 f7c11c38
I/DEBUG ( 113): 80050abc 1c20e828 e818f7c1 18294868 f7c11c38
I/DEBUG ( 113): 80050acc 7987e8ce 2f654b5e 58efd110 29006839
I/DEBUG ( 113): 80050adc 485fdd09 4c624a5b 18a9182b 192a3304
I/DEBUG ( 113):
I/DEBUG ( 113): stack:
I/DEBUG ( 113): 100ffa50 ae604fe5 /system/lib/libril.so
I/DEBUG ( 113): 100ffa54 00000000
I/DEBUG ( 113): 100ffa58 00100000
I/DEBUG ( 113): 100ffa5c 80059c81 /system/lib/libhtc_ril.so
I/DEBUG ( 113): 100ffa60 800747a8
I am now back to my backup (#28 but switched kernel to HCDR.Kernel_4.1). With this kernel wifi is not very stable but at least I can use my phone for calls ;-).
After succesful boot with HCDR.Kernel_4.1, I use SetCPU to set 264MHz Min and 518MHz Max using interactive scaling. Afterwards I may install HCDR.Kernel_4.2 and use this, which has better WIFI and mobile data for me.
Regards
Mirko

Tried libhtc_ril_2.2.0110HM as well, still drops calls for me.

mfriedenhagen said:
Tried libhtc_ril_2.2.0110HM as well, still drops calls for me.
Click to expand...
Click to collapse
Stick with the fixed libril from Post #3972 , which seems to work for everybody. (Didnt get a failure report yet when I went through the thread.)

Please try arco's new test kernel here and report on the nightly thread whether it works or not.

nhnt11 said:
Please try arco's new test kernel here and report on the nightly thread whether it works or not.
Click to expand...
Click to collapse
Would like to reply on the nigthly thread but am still not allowed as I have not created enough posts .
What I did:
- Coming from a nightly #28 and libhtc_ril.so from 3972
- Booted into Recovery
- Cleaned cache and dalvik-cache.
- Installed nightly #28 and kernel from 4104 in one go
- Rebooted
- Signal drops during call when screen goes blank, service provider is gone and reappears after a few seconds.
Code:
W/InputManagerService( 167): Starting input on non-focused client [email protected] (uid=10011 pid=925)
D/AccelerometerListener( 392): orientation: horizontal
D/AccelerometerListener( 392): orientation: vertical
I/power ( 167): *** set_screen_state 0
D/SurfaceFlinger( 167): About to give-up screen, flinger = 0x93778
D/WifiService( 167): ACTION_SCREEN_OFF
I/DEBUG ( 109): *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
I/DEBUG ( 109): Build fingerprint: 'google/passion/passion:2.3.3/GRI40/102588:user/release-keys'
I/DEBUG ( 109): pid: 1127, tid: 1128 >>> /system/bin/rild <<<
I/DEBUG ( 109): signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 00000004
I/DEBUG ( 109): r0 100ffb2c r1 00000001 r2 000000ff r3 00000000
I/DEBUG ( 109): r4 00000000 r5 000000ff r6 afd41504 r7 100ffb2c
I/DEBUG ( 109): r8 ae604fe5 r9 00000000 10 00100000 fp 00000001
I/DEBUG ( 109): ip 80074820 sp 100ffa90 lr 80050abf pc afd18ca0 cpsr 20000030
D/NetworkCollector( 705): state now IDLE
I/DEBUG ( 109): #00 pc 00018ca0 /system/lib/libc.so (fread)
I/DEBUG ( 109): #01 pc 00050abc /system/lib/libhtc_ril.so (ril_func_screen_state_notified)
I/DEBUG ( 109): #02 pc 00032d18 /system/lib/libhtc_ril.so (ril_request_on_request)
I/DEBUG ( 109): #03 pc 00004348 /system/lib/libril.so
I/DEBUG ( 109): #04 pc 00004cf0 /system/lib/libril.so
I/DEBUG ( 109): #05 pc 00004d3e /system/lib/libril.so
I/DEBUG ( 109): #06 pc 00005344 /system/lib/libril.so (_Z14ril_event_loopv)
I/DEBUG ( 109): #07 pc 0000505a /system/lib/libril.so
I/DEBUG ( 109): #08 pc 00011cf4 /system/lib/libc.so (__thread_entry)
I/DEBUG ( 109): #09 pc 000118a4 /system/lib/libc.so (pthread_create)
I/DEBUG ( 109):
I/DEBUG ( 109): code around pc:
I/DEBUG ( 109): afd18c80 bd101c18 1c15b5f0 b0851c0a 4e4d436a
I/DEBUG ( 109): afd18c90 447e9103 92011c1c d1012a00 e08e2500
I/DEBUG ( 109): afd18ca0 2b00685b 2100da01 1c076061 078289a0
I/DEBUG ( 109): afd18cb0 6be2d572 d16f2a00 58734943 2e00681e
I/DEBUG ( 109): afd18cc0 f7ffd101 89a3fd9d 60602000 d474069a

mfriedenhagen said:
Would like to reply on the nigthly thread but am still not allowed as I have not created enough posts .
What I did:
- Coming from a nightly #28 and libhtc_ril.so from 3972
- Booted into Recovery
- Cleaned cache and dalvik-cache.
- Installed nightly #28 and kernel from 4104 in one go
- Rebooted
- Signal drops during call when screen goes blank, service provider is gone and reappears after a few seconds.
Click to expand...
Click to collapse
Alright thanks for testing, I've told arco about it. We'll see.

Would like to reply on the nigthly thread but am still not allowed as I have not created enough posts .
What I did:
- Coming from a nightly #28 and libhtc_ril.so from 3972
- Booted into Recovery
- Cleaned cache and dalvik-cache.
- Installed nightly #28 and kernel from 4139 in one go
- Rebooted
- Signal does not drop during calls from or to my phone when screen goes blank, service provider is not gone.
- Am able to receive SMS as well.
- WIFI/2G/3G are working.

[CM7] #30 wildfire still drops calls after a few seconds unless applying new kernel
What I did:
- Booted into Recovery
- Cleaned cache and dalvik-cache.
- Installed nightly #30
- Rebooted
- Signal does drop during calls from or to my phone when screen goes blank.
- Booted into Recovery
- Installed kernel from 4139
- Rebooted
- Signal does not drop during calls from or to my phone when screen goes blank, service provider is not gone.
- Am able to receive SMS as well.
- WIFI/2G/3G are working as well.

[ICS][CM9][Development] Camera

Hey,
while 'gliding' through XDA, i found that nearly all other devices which already have got ICS ROM(s) meanwhile have a working or partial working camera. I think it's time to open a thread where we can share information on how to get the camera working. So here it is...
I already did some investigation and tried to get it working. Some progress achieved but still no working or partial working camera. Here's what i did for information and as a base for others who want to try around. Ok, let's go....
- i used the msm7x727 camera lib from this thread: http://forum.xda-developers.com/showthread.php?t=1624018
Read this thread for basic information on how they got camera working. Seem's to me that this is a 'port' of rpmv78's solution for Nexus One. Due to the fact that HTC Hero and Galaxy ACE have same chipsets there should be a chance that it works. Important for Maclaw's ICS: You'll have to rename it to 'camera.msm7x27.so' before putting it to /system/lib/hw or it won't get loaded.
- First try: i used proprietary libs (libcamera.so, liboemcamera.so etc.) from a (STOCK Galaxy ACE) gingerbread ROM. These are:
libarccamera.so
libcamera.so
liboemcamera.so
libs3cjpeg.so
Result is a missing symbol in libs. Here's part of logcat during boot:
----
D/AudioHardwareInterface( 145): setMode(NORMAL)
I/AudioHardware( 145): Set master volume to 1.
I/CameraService( 145): CameraService started (pid=145)
E/HAL ( 145): load: module=/system/lib/hw/camera.msm7x27.so
E/HAL ( 145): Cannot load library: link_image[1965]: 145 could not load needed library 'libcamera.so' for 'camera.msm7x27.so' (reloc_library[1314]: 145 cannot locate '_ZN7android7Overlay5setFdEi'...
E/HAL ( 145): )
E/CameraService( 145): Could not load camera HAL module
----
Than i tried to find out where '_ZN7android7Overlay5setFdEi...' can be found. It is in libui.so (of GB ROM). I didn't check it out, but i hardly doubt that we can simply replace an ICS libui with an GB libui.
- Second try: i used proprietary camera libs from this Hero ROM: http://forum.xda-developers.com/showthread.php?t=1612140
Although these libs are proprietary Hero libs, camera module and HAL loaded but as soon as i start camera, i'll get:
----
V/QualcommCameraHardware( 145): openCameraHardware: call createInstance
D/QualcommCameraHardware( 145): createInstance: E
V/QualcommCameraHardware( 145): Storing the current target type as 1
V/QualcommCameraHardware( 145): constructor EX
V/QualcommCameraHardware( 145): startCamera E
D/memalloc( 453): /dev/pmem: Unmapping buffer base:0x4acc4000 size:3112960 offset:2498560
D/memalloc( 250): /dev/pmem: Freeing buffer base:0x4a408000 size:614400 offset:1884160 fd:240
D/memalloc( 250): /dev/pmem: Freeing buffer base:0x4a49e000 size:614400 offset:2498560 fd:276
D/memalloc( 250): /dev/pmem: Freeing buffer base:0x4a372000 size:614400 offset:1269760 fd:221
V/QualcommCameraHardware( 145): loading liboemcamera at 0xb000ed08
D/dalvikvm( 1034): GC_CONCURRENT freed 252K, 6% free 6747K/7175K, paused 5ms+9ms
I/mm-camera-config( 145): cam_conf fd cfgctrl.camfd:0
I/mm-camera-config( 145): Open config device node : /dev/msm_camera/config0
D/dalvikvm( 1034): GC_FOR_ALLOC freed 26K, 5% free 7010K/7367K, paused 28ms
I/ ( 145): [AWB Calibration]:ctrlfd:29
I/ ( 145): [AWB Calibration] read fuse ID fail
I/ ( 145): [AWB Calibration] cfg.fuse_id_word1:0xa94c86fd
I/ ( 145): [AWB Calibration] cfg.fuse_id_word2:0xa94c8664
I/ ( 145): [AWB Calibration] cfg.fuse_id_word3:0xa94ea124
I/ ( 145): [AWB Calibration] cfg.fuse_id_word4:0xa951db40
E/mm-camera-config( 145): config_init_ctrl: cam_conf_get_sensor_info failed!
W/ThrottleService( 250): unable to find stats for iface rmnet0
W/ActivityManager( 250): Launch timeout has expired, giving up wake lock!
W/ActivityManager( 250): Activity idle timeout for ActivityRecord{413ff410 com.android.camera/.Camera}
D/dalvikvm( 250): GC_CONCURRENT freed 551K, 10% free 9416K/10439K, paused 12ms+8ms
I/InputDispatcher( 250): Application is not responding: AppWindowToken{41309880 token=Token{41396428 ActivityRecord{413ff410 com.android.camera/.Camera}}}. 5005.8ms since event, 5005.6ms since wait started
I/WindowManager( 250): Input event dispatching timed out sending to application AppWindowToken{41309880 token=Token{41396428 ActivityRecord{413ff410 com.android.camera/.Camera}}}
I/Process ( 250): Sending signal. PID: 1034 SIG: 3
I/dalvikvm( 1034): threadid=3: reacting to signal 3
I/dalvikvm( 1034): Wrote stack traces to '/data/anr/traces.txt'
I/Process ( 250): Sending signal. PID: 250 SIG: 3
I/dalvikvm( 250): threadid=3: reacting to signal 3
I/dalvikvm( 250): Wrote stack traces to '/data/anr/traces.txt'
I/Process ( 250): Sending signal. PID: 442 SIG: 3
I/dalvikvm( 442): threadid=3: reacting to signal 3
I/dalvikvm( 442): Wrote stack traces to '/data/anr/traces.txt'
I/Process ( 250): Sending signal. PID: 365 SIG: 3
I/dalvikvm( 365): threadid=3: reacting to signal 3
I/dalvikvm( 365): Wrote stack traces to '/data/anr/traces.txt'
D/dalvikvm( 250): GC_CONCURRENT freed 546K, 9% free 9597K/10439K, paused 4ms+9ms
D/dalvikvm( 250): GC_EXPLICIT freed 76K, 9% free 9600K/10439K, paused 6ms+8ms
E/ActivityManager( 250): ANR in com.android.camera (com.android.camera/.Camera)
E/ActivityManager( 250): Reason: keyDispatchingTimedOut
E/ActivityManager( 250): Load: 7.27 / 3.0 / 1.11
E/ActivityManager( 250): CPU usage from 12799ms to 2797ms ago:
E/ActivityManager( 250): 3.9% 250/system_server: 2.9% user + 1% kernel / faults: 83 minor
E/ActivityManager( 250): 1.7% 68/bma_wq: 0% user + 1.7% kernel
E/ActivityManager( 250): 0.5% 64/synaptics_wq: 0% user + 0.5% kernel
E/ActivityManager( 250): 0.5% 365/com.android.systemui: 0.4% user + 0.1% kernel / faults: 4 minor
E/ActivityManager( 250): 0.5% 442/com.android.phone: 0.4% user + 0.1% kernel / faults: 1 minor
E/ActivityManager( 250): 0.3% 27/ksmd: 0% user + 0.3% kernel
E/ActivityManager( 250): 0.1% 5/events/0: 0% user + 0.1% kernel
E/ActivityManager( 250): 0.1% 15/kondemand/0: 0% user + 0.1% kernel
E/ActivityManager( 250): 0% 61/file-storage: 0% user + 0% kernel
E/ActivityManager( 250): 0.1% 65/check_ic_wq: 0% user + 0.1% kernel
E/ActivityManager( 250): 0% 101/jbd2/stl13-8: 0% user + 0% kernel
E/ActivityManager( 250): 0% 139/vold: 0% user + 0% kernel / faults: 51 minor
E/ActivityManager( 250): 0% 218/logcat: 0% user + 0% kernel
E/ActivityManager( 250): 4.3% TOTAL: 2.8% user + 1.4% kernel
E/ActivityManager( 250): CPU usage from 587ms to 1122ms later with 99% awake:
E/ActivityManager( 250): 11% 250/system_server: 5.5% user + 5.5% kernel
E/ActivityManager( 250): 9.2% 318/InputDispatcher: 1.8% user + 7.4% kernel
E/ActivityManager( 250): 1.8% 252/GC: 1.8% user + 0% kernel
E/ActivityManager( 250): 1% 15/kondemand/0: 0% user + 1% kernel
E/ActivityManager( 250): 7.5% TOTAL: 7.5% user + 0% kernel
D/dalvikvm( 250): GC_FOR_ALLOC freed 323K, 10% free 9486K/10503K, paused 74ms
----
The problem seem's to be here: 'E/mm-camera-config( 145): config_init_ctrl: cam_conf_get_sensor_info failed!'. Combining 'solution 2' together with liboemcamera.so from a stock ACE GB-Rom resulted in crashing libcamera.so.
Now let's start to try and discuss to finally get it working....

Hey lagloose how are you doing.... I have tried to get the camera working on many occasions, keep getting the same errors u mentioned above. Thanks for opening this thread, it should boost development a bit

djsky2011 said:
Hey lagloose how are you doing.... I have tried to get the camera working on many occasions, keep getting the same errors u mentioned above. Thanks for opening this thread, it should boost development a bit
Click to expand...
Click to collapse
Thanx for asking So far so good... Lot of work and family business the last weeks...
Hope we'll get the stuff working. Cant' be that all others can, but we don't...

I will try.

Hope the camera can use sooner
Sent from my GT-S5830 using xda premium

The first thing we need to do is look at other similar devices that has camera working and even Pm a few of their devs. A place to start would be the xperia x10 guys
Sent from my GT-S5830 using xda premium

If I remember marcin has a repo which has camera modded for gio.....I see him using GB libs in the prebuilt folder , at the root there is a functions.txt which stores all the Camera functions that can be extracted from libcamera.so (readelf -a -w)
I tried doing that but I don't know how he does the functions format.....
This was sent from a Galaxy Ace. Problem?

Good to see a new thread for CM9 camera!
now maybe we will get working camera on SGA

As Always Samsung did everything different, the hero libs won't work cause the kernel driver is different and the sensor detection fails. You could port the kernel driver to the ace.
When you try to load the original samsung lib there is a bunch of libs you need to load. You could at first try to stub those functions to just get it loading, but the problem is, the comple overlay code was removed in ICS so this will be hard. But doable.

For further information, here's where the stuff crashes when using liboemcamera from stock ACE ROM and libcamera from Hero:
---
I/CameraService( 1676): Opening camera 0
D/CameraHAL( 1676): qcamera_device_open: name:0 device:0x13dfc cameraId:0
V/QualcommCameraHardware( 1676): openCameraHardware: call createInstance
D/QualcommCameraHardware( 1676): createInstance: E
V/QualcommCameraHardware( 1676): Storing the current target type as 1
V/QualcommCameraHardware( 1676): constructor EX
V/QualcommCameraHardware( 1676): startCamera E
V/QualcommCameraHardware( 1676): loading liboemcamera at 0xb000ed08
F/libc ( 1676): Fatal signal 11 (SIGSEGV) at 0x00000000 (code=1)
D/dalvikvm( 1685): GC_CONCURRENT freed 57K, 5% free 7130K/7431K, paused 4ms+4ms
D/dalvikvm( 942): GC_CONCURRENT freed 380K, 9% free 7107K/7751K, paused 3ms+4ms
I/DEBUG ( 1677): *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
I/DEBUG ( 1677): Build fingerprint: 'samsung/cm_cooper/cooper:4.0.4/IMM76D/eng.maclaw.20120414.123054:eng/test-keys'
I/DEBUG ( 1677): pid: 1676, tid: 1676 >>> /system/bin/mediaserver <<<
I/DEBUG ( 1677): signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 00000000
I/DEBUG ( 1677): r0 00000000 r1 a968a665 r2 a9691a90 r3 ffffff40
I/DEBUG ( 1677): r4 000145bc r5 a96916a4 r6 a9691878 r7 a968e338
I/DEBUG ( 1677): r8 00000000 r9 00000000 10 00000000 fp 00000000
I/DEBUG ( 1677): ip 00000064 sp beee1868 lr b00067a0 pc a968bd56 cpsr 60000030
I/DEBUG ( 1677): d0 0000000000000000 d1 0000000000000000
I/DEBUG ( 1677): d2 7e37e43c8800759c d3 0000000000000000
I/DEBUG ( 1677): d4 0000000000000000 d5 7e37e43c8800759c
I/DEBUG ( 1677): d6 3ff0000000000000 d7 3ff0000000000000
I/DEBUG ( 1677): d8 0000000000000000 d9 0000000000000000
I/DEBUG ( 1677): d10 0000000000000000 d11 0000000000000000
I/DEBUG ( 1677): d12 0000000000000000 d13 0000000000000000
I/DEBUG ( 1677): d14 0000000000000000 d15 0000000000000000
I/DEBUG ( 1677): scr 20000000
I/DEBUG ( 1677):
I/DEBUG ( 1677): #00 pc 0000bd56 /system/lib/libcamera.so (_ZN7android22QualcommCameraHardware11startCameraEv)
I/DEBUG ( 1677): #01 pc 0000d9f4 /system/lib/libcamera.so (_ZN7android22QualcommCameraHardware14createInstanceEv)
I/DEBUG ( 1677): #02 pc 0000db34 /system/lib/libcamera.so (openCameraHardware)
I/DEBUG ( 1677): #03 pc 0000260e /system/lib/hw/camera.msm7x27.so (_Z19qcamera_device_openPK11hw_module_tPKcPP11hw_device_t)
I/DEBUG ( 1677): #04 pc 0000ab7c /system/lib/libcameraservice.so (_ZN7android13CameraService7connectERKNS_2spINS_13ICameraClientEEEi)
I/DEBUG ( 1677): #05 pc 00016b42 /system/lib/libcamera_client.so (_ZN7android15BnCameraService10onTransactEjRKNS_6ParcelEPS1_j)
I/DEBUG ( 1677): #06 pc 00008e42 /system/lib/libcameraservice.so (_ZN7android13CameraService10onTransactEjRKNS_6ParcelEPS1_j)
I/DEBUG ( 1677): #07 pc 00017f3c /system/lib/libbinder.so (_ZN7android7BBinder8transactEjRKNS_6ParcelEPS1_j)
I/DEBUG ( 1677): #08 pc 0001b3c4 /system/lib/libbinder.so (_ZN7android14IPCThreadState14executeCommandEi)
I/DEBUG ( 1677): #09 pc 0001b594 /system/lib/libbinder.so (_ZN7android14IPCThreadState14joinThreadPoolEb)
I/DEBUG ( 1677): #10 pc 00008ab6 /system/bin/mediaserver
I/DEBUG ( 1677): #11 pc 000164ea /system/lib/libc.so (__libc_init)
I/DEBUG ( 1677):
I/DEBUG ( 1677): code around pc:
I/DEBUG ( 1677): a968bd34 68206018 eab2f7fb 58a94a92 49926008 .` h.....J.X.`.I
I/DEBUG ( 1677): a968bd44 44796820 eaaaf7fb 49914b90 447958ea hyD.....K.I.XyD
I/DEBUG ( 1677): a968bd54 60016010 6820498f f7fb4479 4b8eeaa0 .`.`.I hyD.....K
I/DEBUG ( 1677): a968bd64 58ea498e 60104479 498d6001 44796820 .I.XyD.`.`.I hyD
I/DEBUG ( 1677): a968bd74 ea94f7fb 498c4b8b 447958ea 60016010 .....K.I.XyD.`.`
I/DEBUG ( 1677):
I/DEBUG ( 1677): code around lr:
I/DEBUG ( 1677): b0006780 02800016 08bd87f0 e5964000 e5967000 [email protected]
I/DEBUG ( 1677): b0006790 e2144903 1a00000e e5965000 ebffec5c .I.......P..\...
I/DEBUG ( 1677): b00067a0 e2055a02 e3853001 e1500003 0a000006 .Z...0....P.....
I/DEBUG ( 1677): b00067b0 e5865000 e1a00006 e1a01005 e3a02001 .P........... ..
I/DEBUG ( 1677): b00067c0 ebffffda e1a00004 e8bd87f0 e3a00000 ................
I/DEBUG ( 1677):
I/DEBUG ( 1677): stack:
I/DEBUG ( 1677): beee1828 a968e338 /system/lib/libcamera.so
I/DEBUG ( 1677): beee182c b000594f /system/bin/linker
I/DEBUG ( 1677): beee1830 b000ed08
I/DEBUG ( 1677): beee1834 a968ff01 /system/lib/libcamera.so
I/DEBUG ( 1677): beee1838 a968bd4d /system/lib/libcamera.so
I/DEBUG ( 1677): beee183c a968e338 /system/lib/libcamera.so
I/DEBUG ( 1677): beee1840 00000000
I/DEBUG ( 1677): beee1844 00000000
I/DEBUG ( 1677): beee1848 00000000
I/DEBUG ( 1677): beee184c b00059f7 /system/bin/linker
I/DEBUG ( 1677): beee1850 a96916a4 /system/lib/libcamera.so
I/DEBUG ( 1677): beee1854 b000ed08
I/DEBUG ( 1677): beee1858 000145bc [heap]
I/DEBUG ( 1677): beee185c a96916a4 /system/lib/libcamera.so
I/DEBUG ( 1677): beee1860 df0027ad
I/DEBUG ( 1677): beee1864 00000000
I/DEBUG ( 1677): #00 beee1868 00000000
I/DEBUG ( 1677): beee186c 400ecf01 /system/lib/libutils.so
I/DEBUG ( 1677): beee1870 000146e0 [heap]
I/DEBUG ( 1677): beee1874 00014510 [heap]
I/DEBUG ( 1677): beee1878 a96916a4 /system/lib/libcamera.so
I/DEBUG ( 1677): beee187c 00014510 [heap]
I/DEBUG ( 1677): beee1880 beee1954 [stack]
I/DEBUG ( 1677): beee1884 000001d0
I/DEBUG ( 1677): beee1888 a96916a4 /system/lib/libcamera.so
I/DEBUG ( 1677): beee188c a968d9f9 /system/lib/libcamera.so
I/DEBUG ( 1677): #01 beee1890 0000f6d0 [heap]
I/DEBUG ( 1677): beee1894 beee1978 [stack]
I/DEBUG ( 1677): beee1898 00013f88 [heap]
I/DEBUG ( 1677): beee189c 00000000
I/DEBUG ( 1677): beee18a0 00000000
I/DEBUG ( 1677): beee18a4 00000000
I/DEBUG ( 1677): beee18a8 00000000
I/DEBUG ( 1677): beee18ac 00002eda
I/DEBUG ( 1677): beee18b0 0000000b
I/DEBUG ( 1677): beee18b4 00000000
I/DEBUG ( 1677): beee18b8 00000000
I/DEBUG ( 1677): beee18bc 00000323
I/DEBUG ( 1677): beee18c0 000041ed
I/DEBUG ( 1677): beee18c4 00000002
I/DEBUG ( 1677): beee18c8 00000000
I/DEBUG ( 1677): beee18cc 00000000
I/DEBUG ( 1677): beee18d0 00000000
I/DEBUG ( 1677): beee18d4 00000000
I/DEBUG ( 1677): beee18d8 00000000
I/DEBUG ( 1677): beee18dc 00000000
I/DEBUG ( 1677): beee18e0 000002f8
I/DEBUG ( 1677): beee18e4 00000000
I/DEBUG ( 1677): beee18e8 00001000
I/DEBUG ( 1677): beee18ec 00000000
I/DEBUG ( 1677): beee18f0 00000000
I/DEBUG ( 1677): beee18f4 00000000
I/DEBUG ( 1677): beee18f8 4fc5dd55
I/DEBUG ( 1677): beee18fc 245bdc83
I/DEBUG ( 1677): beee1900 4fc5dd55
I/DEBUG ( 1677): beee1904 245bdc83
I/DEBUG ( 1677): beee1908 4fc5dd55
I/DEBUG ( 1677): beee190c 245bdc83
I/DEBUG ( 1677): beee1910 00000323
I/DEBUG ( 1677): beee1914 00000000
I/DEBUG ( 1677): beee1918 00014510 [heap]
I/DEBUG ( 1677): beee191c beee1954 [stack]
I/DEBUG ( 1677): beee1920 00001c16
I/DEBUG ( 1677): beee1924 beee1954 [stack]
I/DEBUG ( 1677): beee1928 00001c16
I/DEBUG ( 1677): beee192c 00000000
I/DEBUG ( 1677): beee1930 00013dfc [heap]
I/DEBUG ( 1677): beee1934 a968db39 /system/lib/libcamera.so
I/BootReceiver( 325): Copying /data/tombstones/tombstone_04 to DropBox (SYSTEM_TOMBSTONE)
E/CameraHolder( 1685): fail to connect Camera
E/CameraHolder( 1685): java.lang.RuntimeException: Fail to connect to camera service
E/CameraHolder( 1685): at android.hardware.Camera.native_setup(Native Method)
E/CameraHolder( 1685): at android.hardware.Camera.<init>(Camera.java:320)
E/CameraHolder( 1685): at android.hardware.Camera.open(Camera.java:280)
E/CameraHolder( 1685): at com.android.camera.CameraHolder.open(CameraHolder.java:131)
E/CameraHolder( 1685): at com.android.camera.Util.openCamera(Util.java:267)
E/CameraHolder( 1685): at com.android.camera.Camera$4.run(Camera.java:1118)
E/CameraHolder( 1685): at java.lang.Thread.run(Thread.java:856)
W/AudioSystem( 325): AudioFlinger server died!
I/ServiceManager( 138): service 'media.audio_flinger' died
I/ServiceManager( 138): service 'media.player' died
I/ServiceManager( 138): service 'media.camera' died
I/ServiceManager( 138): service 'media.audio_policy' died
W/AudioSystem( 325): AudioPolicyService server died!
W/MediaMetadataRetriever( 942): MediaMetadataRetriever server died!
W/Camera ( 1685): Camera server died!
---
AFAIK Gio has a semi working camera. Perhaps someone could check if liboemcamera from Maclaws Gio Port works ? I'm in office at the moment and can't do this right now.

camera work perfectly on X8
today, I saw a good thing, that the camera works perfectly on X8 with minicm9, try this: http://forum.xda-developers.com/showthread.php?t=1575094
hope can help you for reference
sorry for my bad english

Samsung changed a bunch of stuff in thier libcameraoem, those changes made it incompatible with the libcamera from qualcode which the hero is using. That lib is opensource an basicly a wrapper around the libcameraoem to abstact the AOSP interface from the verndors code.
If you can you can try to load the libcameraoem stuff, if that works, the rest should be straight forwared. I did some work on it in the early CM days but got lazy an used the blobs.

coolya said:
As Always Samsung did everything different, the hero libs won't work cause the kernel driver is different and the sensor detection fails. You could port the kernel driver to the ace.
When you try to load the original samsung lib there is a bunch of libs you need to load. You could at first try to stub those functions to just get it loading, but the problem is, the comple overlay code was removed in ICS so this will be hard. But doable.
Click to expand...
Click to collapse
You are talking about missing symbol(s) like ''_ZN7android7Overlay5setFdEi...' Right ?
Then what about this: http://review.cyanogenmod.com/#/c/13317/ ?

This changes are required to get the binder working with gingerbread and froyo libs where the binder interface was different.
The binder is just used for IPC you still need to get the overlay stuff working.
I didn't put any work in porting gingerbread camera libs to ics, so I can't tell you much whats needed.

lagloose said:
You are talking about missing symbol(s) like ''_ZN7android7Overlay5setFdEi...' Right ?
Then what about this: http://review.cyanogenmod.com/#/c/13317/ ?
Click to expand...
Click to collapse
says on the page that you linked it's already merged, so it should already work.

Thats just gave me an idea. Coolya could you make a list of suggested methods i'll be be happy to work at this and get it done once and for all.

You can have a look at this first:
https://github.com/CyanogenMod/andr...c327e94a/libcamera/QualcommCameraHardware.cpp
it is some kind of blue print, it is used on other msm7277 device like the Z71 or ZTE Blade to get the camera working. But it won't work OOTB samsung changed a bunch of stuff. I would suggest to get this working with gingerbread and then porting it to ICS schould be not that hard.

look at this thread: http://forum.xda-developers.com/showthread.php?t=1651530
They've collected a lot of informational links in the first post(s) which could help us also...

Wonderful to see you guys working on the camera libs. I have mentioned previously on the general and dev threads that if Blade and P500 can do it so can our devs. One thing that seems to have had an effect for those and other devices with working, or partially working, cameras is some kind of "fix" in the init files. I have experimented myself with various libs with similar results as those posted here but I feel that if we can get a little guidance from the successful devs that will be the way to make progress. Good luck in your quest.
I found that using Retro Camera and OS Monitor helped to assess what was going wrong during my experiments along with catlog of course

djsky2011 said:
Thats just gave me an idea. Coolya could you make a list of suggested methods i'll be be happy to work at this and get it done once and for all.
Click to expand...
Click to collapse
djsky do you have actual Sources/Configs from Maclaw ?

[GUIDE + Microphone Fix][NOOB Friendly] Port CM9 / CM10 Based Roms

Intro​
Code:
/* Last Time i got multiple Requests how to FIX Ril in CM9/CM10 Based Roms
/* Now, i figured out how to get the Mic working and how to port the
/* CM10/CM9 Based Roms, with extended explaining how to and
/* logcats with the problem what needs to be fixed!
/* This Thread tell you all Informations and will show Picture based
/* Informations also ;)
Now lets start ^^
Step 1​
Its quietly easy:
-extract both Roms in two folders, like the base Rom (CM9/CM10 from your Device) in a Folder named Port and the (CM9/CM10 based) Rom from the Device from that u wanna port in a Folder like "Orig/Original"
Picture:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
- Now delete the following Folders in "Port" Folder (the specific folders are placed in /system): /app ; /framework ; /fonts ; /media
Picture:
- Open both Folders once more and move the /app ; /framework ; /fonts ; /media folder from "Original/system" Folder in the "Port/system" Folder
Picture:
-Now u have the basic thing in it
Click to expand...
Click to collapse
Step 2​
- now delete from the "Port/system/lib" Folder this File: android_runtime.so
- Now move the android_runtime.so from the "Original/system/lib" Folder in the "Port/system/lib" Folder ^^
Picture:
- Now u need to modify the build.prop (Notepad++)! Open both in Notepad+ and delete the "ro.build.description=
ro.build.fingerprint=" Line from the original build.prop!
- Open the build.prop from the "Original/system Folder" and copy the "ro.build.description=
ro.build.fingerprint=" Lines
- Now re-open the build.prop from the the "Port/system" Folder and paste the lines below "# Do not try to parse ro.build.description or .fingerprint" Line!
Picture:
Now save it
-Zip all Folders and Files in the "Port" Folder!
-Try to flash it and try to BOOT it ... (I think that it wont boot)
Click to expand...
Click to collapse
Step 3​
I think it wont boot (U will see a long time the Bootanimation and nothing will happen)
Its just a lib related error:
Code:
F/libc ( 449): Fatal signal 11 (SIGSEGV) at 0xdeadbaad (code=1)
I/DEBUG ( 117): *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
I/DEBUG ( 117): Build fingerprint: 'lge/thunderg/thunderg:2.3.3/GRI40/LG-P500-V20h.19D34B612E:user/release-keys'
I/DEBUG ( 117): pid: 449, tid: 449 >>> system_server <<<
I/DEBUG ( 117): signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr deadbaad
I/DEBUG ( 117): r0 deadbaad r1 0000000c r2 00000027 r3 40000000
I/DEBUG ( 117): r4 00000000 r5 00000080 r6 4b048987 r7 be9f9778
I/DEBUG ( 117): r8 40813200 r9 00000006 10 46218e1c fp fffffe50
I/DEBUG ( 117): ip ffffffff sp be9f9740 lr 4001f377 pc 4001b7c2 cpsr 00000030
I/DEBUG ( 117): d0 3fe99999a0000000 d1 3ff0000000000000
I/DEBUG ( 117): d2 bebbbc6c1a570a20 d3 3f1155e54e7e8408
I/DEBUG ( 117): d4 bfb1be5a93a83e1d d5 4000000000000000
I/DEBUG ( 117): d6 4a066ec000000000 d7 000000344d520d0c
I/DEBUG ( 117): d8 0000000000000000 d9 0000000000000000
I/DEBUG ( 117): d10 0000000000000000 d11 0000000000000000
I/DEBUG ( 117): d12 0000000000000000 d13 0000000000000000
I/DEBUG ( 117): d14 0000000000000000 d15 0000000000000000
I/DEBUG ( 117): scr 80000010
I/DEBUG ( 117):
I/DEBUG ( 117): #00 pc 000177c2 /system/lib/libc.so
I/DEBUG ( 117): #01 pc 0000c658 /system/lib/libnativehelper.so (jniRegisterNativeMethods)
I/DEBUG ( 117):
I/DEBUG ( 117): code around pc:
I/DEBUG ( 117): 4001b7a0 1c2bd00c 2d00682d e027d1fb 2a0068da ..+.-h.-..'..h.*
I/DEBUG ( 117): 4001b7b0 4b16d004 447b2001 47906018 22274814 ...K. {D.`.G.H'"
I/DEBUG ( 117): 4001b7c0 70022580 ef6ef7f4 f7f62106 aa01e80c .%.p..n..!......
I/DEBUG ( 117): 4001b7d0 05692400 60546091 20061c11 f7f59401 .$i..`T`... ....
I/DEBUG ( 117): 4001b7e0 a905ebc8 20022200 ebd0f7f5 ef5af7f4 .....". ......Z.
I/DEBUG ( 117):
I/DEBUG ( 117): code around lr:
I/DEBUG ( 117): 4001f354 4b0db5f0 447bb083 681c2600 68a59001 ...K..{D.&.h...h
I/DEBUG ( 117): 4001f364 e0086867 5ea8220c dd032800 99011c28 gh...".^.(..(...
I/DEBUG ( 117): 4001f374 43064788 3f013554 6824d5f4 d1ee2c00 .G.CT5.?..$h.,..
I/DEBUG ( 117): 4001f384 1c30b003 46c0bdf0 0002818e 1c0fb5f0 ..0....F........
I/DEBUG ( 117): 4001f394 b0891c3d a9064355 604d9103 90064914 =...UC....M`.I..
I/DEBUG ( 117):
I/DEBUG ( 117): memory map around addr deadbaad:
I/DEBUG ( 117): be9da000-be9fa000 [stack]
I/DEBUG ( 117): (no map for address)
I/DEBUG ( 117): (no map above)
I/DEBUG ( 117):
I/DEBUG ( 117): stack:
I/DEBUG ( 117): be9f9700 00000002
I/DEBUG ( 117): be9f9704 7b4c2d14
I/DEBUG ( 117): be9f9708 40047774 /system/lib/libc.so
I/DEBUG ( 117): be9f970c 4004c8bc
I/DEBUG ( 117): be9f9710 00000000
I/DEBUG ( 117): be9f9714 4001f377 /system/lib/libc.so
I/DEBUG ( 117): be9f9718 4b04753a /system/lib/libandroid_servers.so
I/DEBUG ( 117): be9f971c 4001e0dd /system/lib/libc.so
I/DEBUG ( 117): be9f9720 ffffffff
I/DEBUG ( 117): be9f9724 00000000
I/DEBUG ( 117): be9f9728 00000000
I/DEBUG ( 117): be9f972c 4b048987 /system/lib/libandroid_servers.so
I/DEBUG ( 117): be9f9730 be9f9778 [stack]
I/DEBUG ( 117): be9f9734 4001e4f5 /system/lib/libc.so
I/DEBUG ( 117): be9f9738 df0027ad
I/DEBUG ( 117): be9f973c 00000000
I/DEBUG ( 117): #00 be9f9740 00000002
I/DEBUG ( 117): be9f9744 00000100
I/DEBUG ( 117): be9f9748 4b045169 /system/lib/libandroid_servers.so
I/DEBUG ( 117): be9f974c 7b4c2d14
I/DEBUG ( 117): be9f9750 0000002b
I/DEBUG ( 117): be9f9754 fffffbdf
I/DEBUG ( 117): be9f9758 0000f2c8 [heap]
I/DEBUG ( 117): be9f975c 40849fdd /system/lib/libdvm.so
I/DEBUG ( 117): be9f9760 0000f2c8 [heap]
I/DEBUG ( 117): be9f9764 401d665b /system/lib/libnativehelper.so
I/DEBUG ( 117): #01 be9f9768 40849fdd /system/lib/libdvm.so
I/DEBUG ( 117): be9f976c 401d665b /system/lib/libnativehelper.so
I/DEBUG ( 117): be9f9770 4b04aac4 /system/lib/libandroid_servers.so
I/DEBUG ( 117): be9f9774 00000004
I/DEBUG ( 117): be9f9778 0000f2c8 [heap]
I/DEBUG ( 117): be9f977c 74800019
I/DEBUG ( 117): be9f9780 00000028
I/DEBUG ( 117): be9f9784 4b048987 /system/lib/libandroid_servers.so
I/DEBUG ( 117): be9f9788 0000f2c8 [heap]
I/DEBUG ( 117): be9f978c 00012830 [heap]
I/DEBUG ( 117): be9f9790 00000000
I/DEBUG ( 117): be9f9794 4b04522d /system/lib/libandroid_servers.so
I/DEBUG ( 117): be9f9798 00012b88 [heap]
I/DEBUG ( 117): be9f979c 4b0473c1 /system/lib/libandroid_servers.so
I/DEBUG ( 117): be9f97a0 001fc710 [heap]
I/DEBUG ( 117): be9f97a4 00012830 [heap]
I/DEBUG ( 117): be9f97a8 00000000
I/DEBUG ( 117): be9f97ac 4b0473ef /system/lib/libandroid_servers.so
D/Zygote ( 408): Process 449 terminated by signal (11)
I/Zygote ( 408): Exit zygote because system server (449) has terminated
What is easy to fix: Replace the android_servers.so in "Port/system/lib" Folder with the one in Original/system/lib Folder
Picture:
Now re-zip all Files and Folders in the /Port Folder and it should boot now after u flashed it!
Click to expand...
Click to collapse
Step 4​
Maybe u get always a Phone FC Error or no one can hear u while u are calling someone! :silly:
Thats an Ril related error
Now u think, what should i do, right?
Hmm u need to decompile both framework.jar´s from "Port/system/framework/" and the one from ur base zip like CM9 or CM10 from your device!
u need apktool for that, its not related for framework.jar´s when u have a gingerbread apktool (1.4.3) or an ics one! its only related that u know how to decompile, recompile and repack the jar (winrar)
rename the framework.jar from your CM9 or CM10 (your Device, NOT FROM THE "PORT" Folder) to framework-orig.jar and put it in apktool folder!
Place the framework.jar from the "Port" folder also in the apktool folder
Now 2 simple commands in apktool cmd window:
Code:
apktool d framework-orig.jar
and
Code:
apktool d framework.jar
let it decompile and close the window only when there is a word: "Done"!
Now open framework.jar.out folder and framework-orig.jar.out folder, yet open in both folders: /smali/com/android/internal/telephony ^^
copy all files which start with RIL and end with .smali and placed in the framework-orig.jar.out/smali/com/android/internal/telephony Folder and put it in the framework.jar.out/smali/com/android/telephony Folder (replace them all)
Some Devices have in build.prop a specific Ril Class Path! Mine is: "ro.telephony.ril_class=JellaxyRIL" urs can variate after the "="! If this is the case, look once more in framewok-orig.jar.out/smali/com/android/internal/telephony and search for "JellaxyRIL" or how ur´s is called after "=" in the RIL Class
Now copy the "JellaxyRIL.smali" (Its the one from my base Rom) or whatever in the other Folder "framework.jar.out/smali/com/android/telephony" !
Now re-compile it:
Code:
apktool b framework.jar.out
let it compile, it takes a few minutes (depends on ur PC Speed)
Now open the framework.jar from "apktool" Folder with WinRAR
and move the classes.dex from "apktool/framework.jar.out/build/apk in the opened WinRAR Window and let it re-pack, now close the Windows (WinRAR) and move the new framework.jar from /apktool in "Port/system/framework"
Voila, Mic Working and no more Phone FC´s!
If u have a problem with it, pm me with the following files:
framework.jar (from the Rom u wanna port), framework.jar (from your base CM10 or CM9) and your build.prop (from ur base CM10 or CM9)
Click to expand...
Click to collapse
Step 6​
May barebone your Rom will improve the stability
Some apps u can remove:
*QuickSearchBox.apk
*STK.apk
*GoogleMail.apk (Mail.apk is still included, so why there should be 2 Mail Apps )
*Term.apk (Terminal Emulator)
*Voice Dialer (Its not the phone and takes also no effect to it)
*VideoEditor.apk (WTF who wants to cut Videos over android 0.o
oh i forgot about that step:
move from "Port/system/etc/permissions" Folder, all Files to "Original/system/etc/permissions" Folder (Replace them) and move them all back to "Port/system/etc/permissions" Folder! One more Thing: if Superuser isn´t working, take the "su File from "Original/system/xbin" and move it to "Port/system/xbin" Folder and replace it!
Click to expand...
Click to collapse

In case the Rom wont boot or u cant do any step bcoz u wont understand it:​
My support: Only over Facebook
Click to expand...
Click to collapse
For the reply "Rom wont boot! Pls help me ", i wont read it!
U need to add the related things i provide now:
Code:
Logcat:
Rom (u wanna port):
Rom Link:
Base Rom:
Base Rom Link:
Your Device:
Click to expand...
Click to collapse

thanks this is what i was waiting for

Messi10 said:
thanks this is what i was waiting for
Click to expand...
Click to collapse
I will provide some guides also, how to port miui jb Or how to port aokp
Sent from my GT-S5660 using xda app-developers app

Pictures and Videos for the Tutorial added, its now n00b proof

The guide is not clear. I mean the first step isn't clear, which folder you name the port ,which folder you name the original, unable to understand.

[GUIDE + Microphone Fix][NOOB Friendly] Port CM9 / CM10 Based Roms

Intro​
Code:
/* Last Time i got multiple Requests how to FIX Ril in CM9/CM10 Based Roms
/* Now, i figured out how to get the Mic working and how to port the
/* CM10/CM9 Based Roms, with extended explaining how to and
/* logcats with the problem what needs to be fixed!
/* This Thread tell you all Informations and will show Picture based
/* Informations also ;)
Now lets start ^^
Step 1​
Its quietly easy:
-extract both Roms in two folders, like the base Rom (CM9/CM10 from your Device) in a Folder named Port and the (CM9/CM10 based) Rom from the Device from that u wanna port in a Folder like "Orig/Original"
Picture:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
- Now delete the following Folders in "Port" Folder (the specific folders are placed in /system): /app ; /framework ; /fonts ; /media
Picture:
- Open both Folders once more and move the /app ; /framework ; /fonts ; /media folder from "Original/system" Folder in the "Port/system" Folder
Picture:
-Now u have the basic thing in it
Click to expand...
Click to collapse
Step 2​
- now delete from the "Port/system/lib" Folder this File: android_runtime.so
- Now move the android_runtime.so from the "Original/system/lib" Folder in the "Port/system/lib" Folder ^^
Picture:
- Now u need to modify the build.prop (Notepad++)! Open both in Notepad+ and delete the "ro.build.description=
ro.build.fingerprint=" Line from the original build.prop!
- Open the build.prop from the "Original/system Folder" and copy the "ro.build.description=
ro.build.fingerprint=" Lines
- Now re-open the build.prop from the the "Port/system" Folder and paste the lines below "# Do not try to parse ro.build.description or .fingerprint" Line!
Picture:
Now save it
-Zip all Folders and Files in the "Port" Folder!
-Try to flash it and try to BOOT it ... (I think that it wont boot)
Click to expand...
Click to collapse
Step 3​
I think it wont boot (U will see a long time the Bootanimation and nothing will happen)
Its just a lib related error:
Code:
F/libc ( 449): Fatal signal 11 (SIGSEGV) at 0xdeadbaad (code=1)
I/DEBUG ( 117): *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
I/DEBUG ( 117): Build fingerprint: 'lge/thunderg/thunderg:2.3.3/GRI40/LG-P500-V20h.19D34B612E:user/release-keys'
I/DEBUG ( 117): pid: 449, tid: 449 >>> system_server <<<
I/DEBUG ( 117): signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr deadbaad
I/DEBUG ( 117): r0 deadbaad r1 0000000c r2 00000027 r3 40000000
I/DEBUG ( 117): r4 00000000 r5 00000080 r6 4b048987 r7 be9f9778
I/DEBUG ( 117): r8 40813200 r9 00000006 10 46218e1c fp fffffe50
I/DEBUG ( 117): ip ffffffff sp be9f9740 lr 4001f377 pc 4001b7c2 cpsr 00000030
I/DEBUG ( 117): d0 3fe99999a0000000 d1 3ff0000000000000
I/DEBUG ( 117): d2 bebbbc6c1a570a20 d3 3f1155e54e7e8408
I/DEBUG ( 117): d4 bfb1be5a93a83e1d d5 4000000000000000
I/DEBUG ( 117): d6 4a066ec000000000 d7 000000344d520d0c
I/DEBUG ( 117): d8 0000000000000000 d9 0000000000000000
I/DEBUG ( 117): d10 0000000000000000 d11 0000000000000000
I/DEBUG ( 117): d12 0000000000000000 d13 0000000000000000
I/DEBUG ( 117): d14 0000000000000000 d15 0000000000000000
I/DEBUG ( 117): scr 80000010
I/DEBUG ( 117):
I/DEBUG ( 117): #00 pc 000177c2 /system/lib/libc.so
I/DEBUG ( 117): #01 pc 0000c658 /system/lib/libnativehelper.so (jniRegisterNativeMethods)
I/DEBUG ( 117):
I/DEBUG ( 117): code around pc:
I/DEBUG ( 117): 4001b7a0 1c2bd00c 2d00682d e027d1fb 2a0068da ..+.-h.-..'..h.*
I/DEBUG ( 117): 4001b7b0 4b16d004 447b2001 47906018 22274814 ...K. {D.`.G.H'"
I/DEBUG ( 117): 4001b7c0 70022580 ef6ef7f4 f7f62106 aa01e80c .%.p..n..!......
I/DEBUG ( 117): 4001b7d0 05692400 60546091 20061c11 f7f59401 .$i..`T`... ....
I/DEBUG ( 117): 4001b7e0 a905ebc8 20022200 ebd0f7f5 ef5af7f4 .....". ......Z.
I/DEBUG ( 117):
I/DEBUG ( 117): code around lr:
I/DEBUG ( 117): 4001f354 4b0db5f0 447bb083 681c2600 68a59001 ...K..{D.&.h...h
I/DEBUG ( 117): 4001f364 e0086867 5ea8220c dd032800 99011c28 gh...".^.(..(...
I/DEBUG ( 117): 4001f374 43064788 3f013554 6824d5f4 d1ee2c00 .G.CT5.?..$h.,..
I/DEBUG ( 117): 4001f384 1c30b003 46c0bdf0 0002818e 1c0fb5f0 ..0....F........
I/DEBUG ( 117): 4001f394 b0891c3d a9064355 604d9103 90064914 =...UC....M`.I..
I/DEBUG ( 117):
I/DEBUG ( 117): memory map around addr deadbaad:
I/DEBUG ( 117): be9da000-be9fa000 [stack]
I/DEBUG ( 117): (no map for address)
I/DEBUG ( 117): (no map above)
I/DEBUG ( 117):
I/DEBUG ( 117): stack:
I/DEBUG ( 117): be9f9700 00000002
I/DEBUG ( 117): be9f9704 7b4c2d14
I/DEBUG ( 117): be9f9708 40047774 /system/lib/libc.so
I/DEBUG ( 117): be9f970c 4004c8bc
I/DEBUG ( 117): be9f9710 00000000
I/DEBUG ( 117): be9f9714 4001f377 /system/lib/libc.so
I/DEBUG ( 117): be9f9718 4b04753a /system/lib/libandroid_servers.so
I/DEBUG ( 117): be9f971c 4001e0dd /system/lib/libc.so
I/DEBUG ( 117): be9f9720 ffffffff
I/DEBUG ( 117): be9f9724 00000000
I/DEBUG ( 117): be9f9728 00000000
I/DEBUG ( 117): be9f972c 4b048987 /system/lib/libandroid_servers.so
I/DEBUG ( 117): be9f9730 be9f9778 [stack]
I/DEBUG ( 117): be9f9734 4001e4f5 /system/lib/libc.so
I/DEBUG ( 117): be9f9738 df0027ad
I/DEBUG ( 117): be9f973c 00000000
I/DEBUG ( 117): #00 be9f9740 00000002
I/DEBUG ( 117): be9f9744 00000100
I/DEBUG ( 117): be9f9748 4b045169 /system/lib/libandroid_servers.so
I/DEBUG ( 117): be9f974c 7b4c2d14
I/DEBUG ( 117): be9f9750 0000002b
I/DEBUG ( 117): be9f9754 fffffbdf
I/DEBUG ( 117): be9f9758 0000f2c8 [heap]
I/DEBUG ( 117): be9f975c 40849fdd /system/lib/libdvm.so
I/DEBUG ( 117): be9f9760 0000f2c8 [heap]
I/DEBUG ( 117): be9f9764 401d665b /system/lib/libnativehelper.so
I/DEBUG ( 117): #01 be9f9768 40849fdd /system/lib/libdvm.so
I/DEBUG ( 117): be9f976c 401d665b /system/lib/libnativehelper.so
I/DEBUG ( 117): be9f9770 4b04aac4 /system/lib/libandroid_servers.so
I/DEBUG ( 117): be9f9774 00000004
I/DEBUG ( 117): be9f9778 0000f2c8 [heap]
I/DEBUG ( 117): be9f977c 74800019
I/DEBUG ( 117): be9f9780 00000028
I/DEBUG ( 117): be9f9784 4b048987 /system/lib/libandroid_servers.so
I/DEBUG ( 117): be9f9788 0000f2c8 [heap]
I/DEBUG ( 117): be9f978c 00012830 [heap]
I/DEBUG ( 117): be9f9790 00000000
I/DEBUG ( 117): be9f9794 4b04522d /system/lib/libandroid_servers.so
I/DEBUG ( 117): be9f9798 00012b88 [heap]
I/DEBUG ( 117): be9f979c 4b0473c1 /system/lib/libandroid_servers.so
I/DEBUG ( 117): be9f97a0 001fc710 [heap]
I/DEBUG ( 117): be9f97a4 00012830 [heap]
I/DEBUG ( 117): be9f97a8 00000000
I/DEBUG ( 117): be9f97ac 4b0473ef /system/lib/libandroid_servers.so
D/Zygote ( 408): Process 449 terminated by signal (11)
I/Zygote ( 408): Exit zygote because system server (449) has terminated
What is easy to fix: Replace the android_servers.so in "Port/system/lib" Folder with the one in Original/system/lib Folder
Picture:
Now re-zip all Files and Folders in the /Port Folder and it should boot now after u flashed it!
Click to expand...
Click to collapse
Step 4​
Maybe u get always a Phone FC Error or no one can hear u while u are calling someone! :silly:
Thats an Ril related error
Now u think, what should i do, right?
Hmm u need to decompile both framework.jar´s from "Port/system/framework/" and the one from ur base zip like CM9 or CM10 from your device!
u need apktool for that, its not related for framework.jar´s when u have a gingerbread apktool (1.4.3) or an ics one! its only related that u know how to decompile, recompile and repack the jar (winrar)
rename the framework.jar from your CM9 or CM10 (your Device, NOT FROM THE "PORT" Folder) to framework-orig.jar and put it in apktool folder!
Place the framework.jar from the "Port" folder also in the apktool folder
Now 2 simple commands in apktool cmd window:
Code:
apktool d framework-orig.jar
and
Code:
apktool d framework.jar
let it decompile and close the window only when there is a word: "Done"!
Now open framework.jar.out folder and framework-orig.jar.out folder, yet open in both folders: /smali/com/android/internal/telephony ^^
copy all files which start with RIL and end with .smali and placed in the framework-orig.jar.out/smali/com/android/internal/telephony Folder and put it in the framework.jar.out/smali/com/android/telephony Folder (replace them all)
Some Devices have in build.prop a specific Ril Class Path! Mine is: "ro.telephony.ril_class=JellaxyRIL" urs can variate after the "="! If this is the case, look once more in framewok-orig.jar.out/smali/com/android/internal/telephony and search for "JellaxyRIL" or how ur´s is called after "=" in the RIL Class
Now copy the "JellaxyRIL.smali" (Its the one from my base Rom) or whatever in the other Folder "framework.jar.out/smali/com/android/telephony" !
Now re-compile it:
Code:
apktool b framework.jar.out
let it compile, it takes a few minutes (depends on ur PC Speed)
Now open the framework.jar from "apktool" Folder with WinRAR
and move the classes.dex from "apktool/framework.jar.out/build/apk in the opened WinRAR Window and let it re-pack, now close the Windows (WinRAR) and move the new framework.jar from /apktool in "Port/system/framework"
Voila, Mic Working and no more Phone FC´s!
If u have a problem with it, pm me with the following files:
framework.jar (from the Rom u wanna port), framework.jar (from your base CM10 or CM9) and your build.prop (from ur base CM10 or CM9)
Click to expand...
Click to collapse
Step 6​
May barebone your Rom will improve the stability
Some apps u can remove:
*QuickSearchBox.apk
*STK.apk
*GoogleMail.apk (Mail.apk is still included, so why there should be 2 Mail Apps )
*Term.apk (Terminal Emulator)
*Voice Dialer (Its not the phone and takes also no effect to it)
*VideoEditor.apk (WTF who wants to cut Videos over android 0.o
oh i forgot about that step:
move from "Port/system/etc/permissions" Folder, all Files to "Original/system/etc/permissions" Folder (Replace them) and move them all back to "Port/system/etc/permissions" Folder! One more Thing: if Superuser isn´t working, take the "su File from "Original/system/xbin" and move it to "Port/system/xbin" Folder and replace it!
Click to expand...
Click to collapse

In case the Rom wont boot or u cant do any step bcoz u wont understand it:​
My support: Only over Facebook
Click to expand...
Click to collapse
For the reply "Rom wont boot! Pls help me ", i wont read it!
U need to add the related things i provide now:
Code:
Logcat:
Rom (u wanna port):
Rom Link:
Base Rom:
Base Rom Link:
Your Device:
Click to expand...
Click to collapse

What about the 2 .emd files in media folder.
Does the Ace need those to boot?
Sent from my LG-VM670 using Tapatalk 2

I really dunno, but i think yes
Sent from my GT-S5660 using xda app-developers app

http://forum.xda-developers.com/showthread.php?t=1598713
edit: do not delete STK.apk, some voip app need it

huh ! i gave one last try and successfully moved all the contents on RIL and also my own device ril.class to the port.
but when i try to compile it, here is the error i am getting
plz help compiling it lol
EDIT = @DQIB sorry for all that spam PM's XD ignore them...
---------- Post added at 09:20 PM ---------- Previous post was at 09:08 PM ----------
ok guys resovled my error myself silly mistake

ImbaWind said:
http://forum.xda-developers.com/showthread.php?t=1598713
edit: do not delete STK.apk, some voip app need it
Click to expand...
Click to collapse
thx for it <
I re-fine the thread later ^^ (EDIT: Its my port version, not a copied one from peteragent5 )

DQiB said:
I really dunno, but i think yes
Sent from my GT-S5660 using xda app-developers app
Click to expand...
Click to collapse
Make sure you don't delete the original ones then. Deleting the 2 EMD files will result in fail boot.
Sent from my LG-VM670 using Tapatalk 2

CM 12.1 Bluetooth bugs?

So I got a smart watch and recently started using Bluetooth.
I was on a nightly, but the Bluetooth would cut out overnight and it would not turn on. So I did a clean flash of the snapshot from Nov 16 2015. That worked great for a few days, but now the Bluetooth is cutting out at night (I use sleep tracking and it only worked for 2 hours after I went to bed).
I'm so aggravated by this, because everywhere I find a relevant post to this problem, they say the Bluetooth bugs have been fixed, but clearly not for the sprint s4.
Thanks

Try this specific date build.
20151113 - Two different builds, check specific build changes below, also check out post #7459
MD5 "BT_ONE" - be774523fa4e2fc7c3d2c134851b97ef
http://forum.xda-developers.com/gal...lop/exclusive-antaresone-alucard24-s-t3066696
It is the only rom that bluetooth ever behaved for me on my sprint phone.

I'll try to get around to trying that, but I just reinstalled all my apps and data, so who knows when I'll get around to it.
Also I just copied the crash report:
*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
Build fingerprint: 'samsung/jfltespr/jfltespr:4.4.2/KOT49H/L720VPUFNG2:user/release-keys'
Revision: '11'
ABI: 'arm'
pid: 2751, tid: 2844, name: bluedroid wake/ >>> com.android.bluetooth <<<
signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x0
r0 b3532de8 r1 00000000 r2 af2d468c r3 af2e5378
r4 00000001 r5 af2e5330 r6 af2c0a73 r7 00000000
r8 af3debbc r9 00002000 sl 00000806 fp 0000000c
ip b6dab1f5 sp a2001d00 lr af28049b pc 00000000 cpsr 600e0010
backtrace:
#00 pc 00000000 <unknown>
#01 pc 000fa499 /system/lib/hw/bluetooth.default.so (vendor_ssrcleanup+12)
#02 pc 0003ab0f /system/lib/hw/bluetooth.default.so (bte_ssr_cleanup+38)
#03 pc 000d8895 /system/lib/hw/bluetooth.default.so (btu_hcif_cmd_timeout+388)
#04 pc 000d8ff5 /system/lib/hw/bluetooth.default.so (btu_task+660)
#05 pc 000a39ad /system/lib/hw/bluetooth.default.so
#06 pc 00014053 /system/lib/libc.so (__pthread_start(void*)+30)
#07 pc 00012083 /system/lib/libc.so (__start_thread+6)
Click to expand...
Click to collapse
Does anyone know if I go back to cm11 (that's Android 4.4.4 correct?), will that have stable Bluetooth? I'm just curious why they haven't been able to get it under control already