Database Info

[BETA][Kernel][Port][GT-P6200]

First I must thank @ aorth, and @ garyd9. Without these guys, this would not be here. Please smash their thanks button when you see them.Thank you guys so much. Much if not all of this is gard9's mod's just ported to our device. In fact until I make any relevant edits this thread will remain tagged [PORT].
Beta 4 up. Stock Clocks and voltages built a version with voltage tables intact, but lowering even one of them by the min(25mV) and applying in SetCpu causes panic.
Beta testers needed. You know the drill. Backup and feedback is always appreciated.
Im almost positive all 6200 kernel partitions are on mmcblk0p5, you can double check with 'get pit' & heimdall. Mobile Odin says it supports P6200 and works fine. I honestly can not say for sure, but Im 99% confident this is the case. Those with any rare models, please be Warned!Flashing a kernel to the incorrect partition is asking to be bricked.--please put both custom and stock on sdcard in case you cannot boot.--
The 2 .zips that have zImage at the end, are to be extracted and flashed with Mobile Odin(recommend Pro to wipe), or heimdall.
Keep in mind if you use Mobile Odin and it doesnt boot, you will be stuck. Good idea to have stock loaded for heimdall, or stock .zip wit CWM Recovery.
The other 2 that start with GT-P6200 can be flashed in recovery. <WARNING>: SOME People have had to wipe /data ; factory reset to get past stuck boot logo.</WARNING> I have updated the install script, so cache and dalvik should be totally cleared.
Either way my custom binary count hasnt changed any.
Features
custom bootanimation support: place appropriate botoanimation.zip in: /system/media/ with permission rw-r--r--. The ICS one garyd made us works lovely. Im using the xda TV one. link coming soon:
Busybox in /sbin.
Support for init.d scripts. (Personal warning about Supercharger scripts: Nitro lag nullifier is OK, but I dont recommend using the I/O tweaks, put me in a boot loop everytime. Be Warned. Also his 3G tweaks made my 3G speeds worse.)
Removed a lot of debug stuff.
unsecure kernel (adb shell gives root)
reboot bootloader and reboot download support
(quick boot in market is a great app)
Enjoy!!

reserved
Beta 4 up: 3/20
Removed OC/UV, stock clocks and voltages. tried a build with Gary's table sysfs in there, UV even one frequency by 25mV and pressing apply in SetCpu caused seizure. At least were stable now. Im not too concerned about battery life. There are other tweaks we can apply.
github: still updating..
https://github.com/crotoloandroid

Established on LA2 (SER). Far so good, thanks.

Putting it through its paces right now
Thanks
SetCPU set to 200 min, 1400 max
OnDemand governor. No other changes.
Nenamark1: 55.6 fps (no previous record)
Nenamark2: 41.1 fps (47.7 fps pre-oc)... very erratic performance
Stability Test, HQ CPU&GPU, 6 minute test: CPU passes, 7. GPU passes, 55. No failures
GL Benchmark v2.1 (All Tests): Passed, however can't upload to GLBenchmark.com as their captcha service is ****ed
Only one issue I've come across so far, and this is the same issue RichardTrip was having when he compiled some custom kernels for me earlier this year. Random wakelocks bring the tab out of sleep and turn the screen on.
These are caused by the usb scanner looking for external USB devices...
Code:
D/UsbService( 3447): setUsbObserverNotification :: titleId = 0, messageId = 0, icon = 17302785, visible = false, dismissable = false
D/usbhost ( 3447): new device /dev/bus/usb/001/004
D/usbhost ( 3447): usb_device_open /dev/bus/usb/001/004
D/usbhost ( 3447): usb_device_new /dev/bus/usb/001/004 fd: 298
D/usbhost ( 3447): usb_device_new read returned 259 errno 4
D/UsbService( 3447): usbDeviceAdded : device :: /dev/bus/usb/001/004 [1519h:0020h] [02h,00h,00h] (CDC Control)
D/UsbService( 3447): isBlackListed :: deviceName = /dev/bus/usb/001/004
D/UsbService( 3447): isBlackListed :: mHostBlacklist[i] = /dev/bus/usb/001/002
E/UsbService( 3447): isBlackListed :: clazz = 2, subClass = 0, protocol = 0
E/UsbService( 3447): isBlackListed :: clazz2 subClass=0
E/UsbService( 3447): continue...
D/UsbService( 3447): usbDeviceAdded : interface :: /dev/bus/usb/001/004 [1519h:0020h] [02h,02h,01h] (CDC Control)
E/UsbService( 3447): isBlackListed :: clazz = 2, subClass = 2, protocol = 1
E/UsbService( 3447): isBlackListed :: clazz2 subClass=2
D/UsbService( 3447): usbDeviceAdded : interface :: /dev/bus/usb/001/004 [1519h:0020h] [0ah,00h,00h] (CDC Data)
E/UsbService( 3447): isBlackListed :: clazz = 10, subClass = 0, protocol = 0
E/NotificationService( 3447): cancelNotification - pkg:android, id:17302785
D/TabletStatusBar( 3529): setVisibility(View.VISIBLE
E/UsbService( 3447): isBlackListed :: clazz10 subClass=0
D/UsbService( 3447): usbDeviceAdded : interface :: /dev/bus/usb/001/004 [1519h:0020h] [02h,02h,01h] (CDC Control)
E/UsbService( 3447): isBlackListed :: clazz = 2, subClass = 2, protocol = 1
E/UsbService( 3447): isBlackListed :: clazz2 subClass=2
D/UsbService( 3447): usbDeviceAdded : interface :: /dev/bus/usb/001/004 [1519h:0020h] [0ah,00h,00h] (CDC Data)
D/dalvikvm( 6436): GC_CONCURRENT freed 358K, 11% free 6800K/7559K, paused 2ms+1ms
E/UsbService( 3447): isBlackListed :: clazz = 10, subClass = 0, protocol = 0
E/UsbService( 3447): isBlackListed :: clazz10 subClass=0
D/KeyguardViewMediator( 3447): setHidden false
D/UsbService( 3447): usbDeviceAdded : interface :: /dev/bus/usb/001/004 [1519h:0020h] [02h,02h,01h] (CDC Control)
E/UsbService( 3447): isBlackListed :: clazz = 2, subClass = 2, protocol = 1
E/UsbService( 3447): isBlackListed :: clazz2 subClass=2
D/UsbService( 3447): usbDeviceAdded : interface :: /dev/bus/usb/001/004 [1519h:0020h] [0ah,00h,00h] (CDC Data)
E/UsbService( 3447): isBlackListed :: clazz = 10, subClass = 0, protocol = 0
E/UsbService( 3447): isBlackListed :: clazz10 subClass=0
D/UsbService( 3447): usbDeviceAdded : interface :: /dev/bus/usb/001/004 [1519h:0020h] [02h,02h,01h] (CDC Control)
E/UsbService( 3447): isBlackListed :: clazz = 2, subClass = 2, protocol = 1
E/UsbService( 3447): isBlackListed :: clazz2 subClass=2
D/UsbService( 3447): usbDeviceAdded : interface :: /dev/bus/usb/001/004 [1519h:0020h] [0ah,00h,00h] (CDC Data)
E/UsbService( 3447): isBlackListed :: clazz = 10, subClass = 0, protocol = 0
E/UsbService( 3447): isBlackListed :: clazz10 subClass=0
D/UsbService( 3447): turnOnLcd ::
D/PowerManagerService( 3447): reactivateScreenLocksLocked mProxIgnoredBecauseScreenTurnedOff=true
I/PowerManagerService( 3447): Ulight 0->3|0
I/PowerManagerService( 3447): setTargetLocked mask=2 curValue=0.0 target=95 targetValue=95 delta=6.3333335 nominalCurrentValue=0
I/PowerManagerService( 3447): scheduling light animator
I/power ( 3447): *** set_screen_state 1
D/KeyguardViewMediator( 3447): onScreenTurnedOn, seq = 3
D/KeyguardViewMediator( 3447): notifyScreenOnLocked
D/KeyguardViewMediator( 3447): handleNotifyScreenOn
D/LockScreen( 3447): updateLayout: status=Normal
D/PowerManagerService( 3447): enableLightSensorLocked enable=true mAutoBrightessEnabled=false
D/PowerManagerService( 3447): jumpToTargetLocked targetValue=95: 2
I/PowerManagerService( 3447): Light Animator Finished curIntValue=95
I/OrientationDebug( 3447): [WindowOrientationListener] in enable(), now call SensorManager.registerListener()
D/SensorManager( 3447): registerListener :: handle = 4 name= MPL accel delay= 60000 Listener= [email protected]0c5dc38
D/MPLSensor( 3447): handle : 4 en: 1
D/MPLSensor( 3447): enabled_sensors: 16 dmp_started: 0
D/MPLSensor( 3447): MLSetMPUSensors: 70
I/MPL-ml ( 3447): Actual ODR: 25 Hz
D/MPLSensor( 3447): set_power_states > MLDmpStart()
I/ ( 3447): mpu3050_resume: Resuming to 0070
D/MPLSensor( 3447): setDelay : handle=4, delay=200000000
I/ ( 3447): mpu3050_suspend: suspending sensors to 0000
I/ ( 3447): mpu3050_suspend: Will resume next to 0070
I/MPL-ml ( 3447): Actual ODR: 25 Hz
I/ ( 3447): mpu3050_resume: Resuming to 0070
D/MPLSensor( 3447): setDelay : handle=4, delay=60000000
I/ ( 3447): mpu3050_suspend: suspending sensors to 0000
I/ ( 3447): mpu3050_suspend: Will resume next to 0070
I/MPL-ml ( 3447): Actual ODR: 25 Hz
I/ ( 3447): mpu3050_resume: Resuming to 0070
V/WindowManager( 3447): Setting event dispatching to true
D/KeyguardViewMediator( 3447): setHidden false
D/WifiStateMachine( 3447): ConnectedState{ what=65659 when=-1ms }
D/WifiStateMachine( 3447): ConnectModeState{ what=65659 when=-1ms }
D/WifiStateMachine( 3447): DriverStartedState{ what=65659 when=-1ms }
D/WifiStateMachine( 3447): SupplicantStartedState{ what=65659 when=-1ms }
E/wpa_supplicant( 3807): initalize the scan timer ( 7 )
D/WifiService( 3447): ACTION_SCREEN_ON
I/ScreenReceiver : ( 4156): android.intent.action.SCREEN_ON
D/ProximityScreenOff( 4156): ScreenReceiver : action = android.intent.action.SCREEN_ON State: IDLEPhoneOn = false
D/WifiStateMachine( 3447): ConnectedState{ what=65618 when=-5ms arg1=1 }
D/SensorManager( 4156): registerListener :: handle = 8 name= GP2A Proximity sensor delay= 10000 Listener= [email protected]
I/ProximityScreenOff( 4156): SensorMonitor onStart::Registered
D/WifiStateMachine( 3447): ConnectedState{ what=65591 when=-12ms }
D/WifiStateMachine( 3447): ConnectModeState{ what=65591 when=-12ms }
D/WifiStateMachine( 3447): DriverStartedState{ what=65591 when=-12ms }
D/WifiStateMachine( 3447): SupplicantStartedState{ what=65591 when=-13ms }
D/WifiStateMachine( 3447): ConnectedState{ what=65608 when=-13ms arg1=1 }
D/WifiStateMachine( 3447): ConnectedState{ what=65549 when=-13ms }
D/WifiStateMachine( 3447): ConnectModeState{ what=65549 when=-13ms }
D/WifiStateMachine( 3447): DriverStartedState{ what=65549 when=-13ms }
D/WifiStateMachine( 3447): SupplicantStartedState{ what=65549 when=-13ms }
D/WifiStateMachine( 3447): DefaultState{ what=65549 when=-14ms }
D/WifiStateMachine( 3447): ConnectedState{ what=65613 when=-14ms }
D/WifiStateMachine( 3447): ConnectModeState{ what=65613 when=-14ms }
D/WifiStateMachine( 3447): DriverStartedState{ what=65613 when=-14ms }
D/JuicePlotter.CollectService( 4252): battery:48, plugged:0, screen:95, wifi:true(0kb/s), apn:false(0kb/s), bluetooth:false,cpu:2
W/googleanalytics( 4331): Store full. Not storing last event.
D/SurfaceFlinger( 3267): Screen about to return, flinger = 0xa920

chrisrotolo said:
1st I must thank @ aorth, and @ garyd. Without these guys, this would not be here. Please smash their thanks button when you see them.Thank you guys so much. Much if not all of this is gard9's mod's just ported to our device.
Beta testers needed. 100% working and stable for me. UWAXME - Malyasia Tab
Im almost positive all 6200 kernel partition is on mmcblk0p5, you can double check with get pit & heimdall. Mobile Odin says it supports P-6200 and works fine. I honestly can not say for sure, but Im 99% confident this is the case. Those with any rare models, please be Warned!--please put both custom and stock on sdcard in case you cannot boot.--
the 2 .zips that have zImage at the end, are to be extracted and flashed with Mobile Odin(recommend Pro to wipe), or heimdall.
Keep in mind if you use Mobile Odin and it doesnt boot, you will be stuck. Good idea to have stock loaded in heimdall, or stock .zip wit CWM Recovery.
the other 2 that start with GT-P6200 can be flashed in recovery.
Either way my custom binary count hasnt changed.
As Im short on time at the moment I will make this brief and update this thread shortly.
contains:
custom bootanimation support place usual in: /system/media/bootanimation.zip with permission rw-r--r--. the ICS one garyd made us works lovely.
OC to 1.4 (NO UV yet, but likely in final release.)
unsecure kernel (adb shell gives root)
and init.d scripts tested with Supercharger. (Personal warning about Supercharger scripts: Nitro lag nullifier is OK, but I dont recommend using the I/O tweaks, put me in a boot loop everytime. Also his 3G tweaks made my actually worse.)
to come: UV, reboot download support, (botologos maybe?), what else? let me know I'll see what I can do. This is my first kernel, Im learning as I go.
This should have been released a week ago, but I was stuck on a permissions issue, that was so easy to fix.
Enjoy!!
Click to expand...
Click to collapse
it great and mega fast i am so pleased we have you on out team bro you are mega awesome....donation on its way.
i installed the cwm version and it wad stuck in boot loop but i wiped data and it worked...thanks got for app extracter haha :-D but well worth it.
thanks man keep up the good work
regards jmar8124 G-tab plus kl3 Malaysia

You had to factory reset? Ill double check my scripts to wipe cache and dalvik

chrisrotolo said:
You had to factory reset? Ill double check my scripts to wipe cache and dalvik
Click to expand...
Click to collapse
ye but it could have been something to do with old tegers haha stupid lum of crap haha its got to be the worst app iv ever purchased. thanos man you kernel is great il try installing it agen with out kernel beeing loaded

Updated my original post above ^^^

double_ofour said:
Pare how can i convert CDL to o2? step-by-step please
Click to expand...
Click to collapse
Thanks chris, will test this. Excited to see some dev going on with international version of 7+. Some suggestions:
Please name your kernel! Make it sound cool as it really is
Add cifs.ko support in the future?
Also just a question, would oc'ng to 1.4 ghz be dangerous without any overvolting. Thanks!
Sent from my GT-P6200 using XDA

download and flash awayyyy.... doing stress test now...
edit...
installation no problem... setting up setcpu now... and doing stress test for max 1400

thanks for the help testing guys. This 1.4 is "hidden" in stock cpufreq commented out as "development only". Should be fine unless you run graphics intense apps with min & man set to 1.4 and performance governor for long periods of time.
I'll add warning about some having to wipe /data with CWM.
I'll look into cifs.ko, should be doable.
I've been getting a lot of dropped signal, may be totally unrelated, I just move to a new building, and also just got word we should be getting AT&T LTE in Hartford CT in a few weeks, so could be network thing.
be back as soon as I can guys. Feedback helps.

u guys getting any deep sleep on cpu spy? im not getting any deep sleep
Edit: a reboot helped got deep sleep back. Reasonable batt life at 1.4ghz

being using it for 2 hours with nova2... current batt from 100% to 60% but full 2 hours on nova... quite ok... runnning setcpu 1400 with ondemand governor... havent face any problem yet...

Flashed the custom kernel with recovery ...everything works just fine.
First boot was a bit long as expected.
I used nofrills cpu control, the default interactive governor was a bit laggy, changed to conservative. No deep sleep problem at all.
Thank you.
Sent from my GT-P6200 using XDA

For anyone interested in cifs.ko or tun.ko, check out this thread...
http://forum.xda-developers.com/showthread.php?t=1400255
Anyone else having wakelocks? / random wake ups? I havent had any.
Welp, likely not going to be able to implement @garyd9's UV, keep getting this mesaage :
arch/arm/mach-s5pv310/built-in.o: In function `s5pv310_set_cpufreq_armvolt':
/home/chris/Desktop/samsung-kernel-p6200/arch/arm/mach-s5pv310/cpufreq.c:735: undefined reference to `exp_UV_mV'
/home/chris/Desktop/samsung-kernel-p6200/arch/arm/mach-s5pv310/cpufreq.c:735: undefined reference to `exp_UV_mV'
arch/arm/mach-s5pv310/built-in.o: In function `s5pv310_cpufreq_init':
/home/chris/Desktop/samsung-kernel-p6200/arch/arm/mach-s5pv310/cpufreq.c:2121: undefined reference to `exp_UV_freq'
/home/chris/Desktop/samsung-kernel-p6200/arch/arm/mach-s5pv310/cpufreq.c:2121: undefined reference to `exp_UV_mV'
make: *** [.tmp_vmlinux1] Error 1
at end of kernel build. The one we have I think should be fine. I will add support for reboot bootloader (& download), and probably release final version tomorrow.
I dont want to make this a long in depth thing anyways (its already been a few weeks for me), becuase hopefully Ice Cream is near.
And my home cpu is in dire need of an upgrade (AMD dual core 4GB) building takes nearly an hour on VM, I will likely be getting a new one shortly.
UPDATE: so I think I am getting wake locks/ USB issue. I think Ive had it wake itself 3 times in a row, and Ive had it lose signal when I press power button to wake device, it signal bars are 0;all grey, and/or says no signal, and occasionally at the same time will says usb device removed.
ive compared my config to garyd9's, at least the one I think he used. didnt see anything I think might cause it, although we do have a bit more hardware in ours. I though I recall something in the kernel menuconfig about wakelocks.
I guess its to be expected, hacking my first kernel. Guess I will just have to run some DMESG's
VENT APPEND: I am finding github push/pull/commit/add/etc to be a steamy pile of crap. I will search for alternatives.

yup got random wake locks... but i haven't face any usb/no signal issue. at least not yet
btw info about governors is quite nice here...
http://forum.xda-developers.com/showthread.php?t=1369817

I found the archive article on wakelocks in galaxy nexus forums. Power management configs are same as garyd9's I believe, maybe because of our always on data connection. Have to look in /proc/wakelocks

chrisrotolo said:
I found the archive article on wakelocks in galaxy nexus forums. Power management configs are same as garyd9's I believe, maybe because of our always on data connection. Have to look in /proc/wakelocks
Click to expand...
Click to collapse
chris,
using cpu spy and betterbatterystats app from xda, i was able to trace my wakelocks to mediascanner. so i just killed mediascanner and i got deep sleep back. im not sure though if i had this problem even before i flashed your custom kernel because i never used cpu spy and betterbatterystats on the stock kernel. maybe this helps? i don't get signal drops

chris... i'm currently testing some of the script for init.d on this thread...
http://forum.xda-developers.com/showthread.php?t=1353903

chrisrotolo said:
I found the archive article on wakelocks in galaxy nexus forums. Power management configs are same as garyd9's I believe, maybe because of our always on data connection. Have to look in /proc/wakelocks
Click to expand...
Click to collapse
im always on wifi, barely use my data plan. but i do have wakelocks draining the battery. i also noticed once that my screen didn't time out, screen was on all the time when i left my tablet, so battery drained quite quickly. i think someone has reported this also. i'll do more observation.

[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

nice guide. gonna try this sometimes

Syfer_Fever said:
nice guide. gonna try this sometimes
Click to expand...
Click to collapse
can u explain me if i want to port CM 10 from mini to my fit so what do i do.
which is the port rom and original rom.
totally confused.
don't understand base rom and etc stuffs. lil explanation need. plz help

creativeguy09 said:
can u explain me if i want to port CM 10 from mini to my fit so what do i do.
which is the port rom and original rom.
totally confused.
don't understand base rom and etc stuffs. lil explanation need. plz help
Click to expand...
Click to collapse
i think you just replace "usr" folder from cm10-beni to ROM you wanna port and replace the kernel with ours, if the ROM dosen't boot try Step 2
if you still confuse maybe you can ask the OP

Syfer_Fever said:
i think you just replace "usr" folder from cm10-beni to ROM you wanna port and replace the kernel with ours, if the ROM dosen't boot try Step 2
if you still confuse maybe you can ask the OP
Click to expand...
Click to collapse
IN FOLDER PORT Put in the Rom from your device! and in ORIGINAL the Rom u wanna port
To Syfer_Fever: Should i ad a video that u understand it? :silly:
It takes no effect if u replace the /usr folder with the same /usr folder!

DQiB said:
IN FOLDER PORT Put in the Rom from your device! and in ORIGINAL the Rom u wanna port
To Syfer_Fever: Should i ad a video that u understand it? :silly:
It takes no effect if u replace the /usr folder with the same /usr folder!
Click to expand...
Click to collapse
video? for me? for what?
to get soft key button works because mini don't have soft button

hi dqib can you make guide how to port stock based rom from other device like gio,y etc...waiting for guide

Syfer_Fever said:
video? for me? for what?
to get soft key button works because mini don't have soft button
Click to expand...
Click to collapse
last time i tell it u!
All files out of /app ,/framework ,/media ,/fonts
are completely the same (BCOZ YOU USE THE LATEST CM9 OR CM10 for GALAXY FIT and not the ROM FROM GALAXY MINI )

DQiB said:
last time i tell it u!
All files out of /app ,/framework ,/media ,/fonts
are completely the same (BCOZ YOU USE THE LATEST CM9 OR CM10 for GALAXY FIT and not the ROM FROM GALAXY MINI )
Click to expand...
Click to collapse
lol relax "mr.all know everything" you are using capslock seems your childish is out
don't be arrogant, you should tell people who don't know nicely

yes my friend yes sir if u will make a video i would be really thankful and grateful to u. i'm following your instructions but a video would be helpful. great work thanks.
by the way as a personal thought which is the best rom to use for fit. i'm using CM7 currently original one.

I make a kitchen for porting ...
It should be easier for u
Sent from my GT-S5660 using xda app-developers app

? Sorry what u saying kitchen? I don't understand
Sent from my GT-S5670 using xda app-developers app

it helps u t odo it! (porting)
U only need to edit the build.prop and zip the rest ^^
(RIL Fix also, thats manual) :laugh:

Please give the link of working kitchen for our Samsung galaxy fit and apktool also. I have a kitchen file but it's only for HTC roms
Sent from my GT-S5670 using Tapatalk 2
---------- Post added at 10:42 PM ---------- Previous post was at 10:39 PM ----------
DQiB said:
I make a kitchen for porting ...
It should be easier for u
Sent from my GT-S5660 using xda app-developers app
Click to expand...
Click to collapse
Please give the link of working kitchen for our Samsung galaxy fit and apktool also. I have a kitchen file but it's only for HTC roms
Sent from my GT-S5670 using Tapatalk 2

[ROM][2.3.8][OFFICIAL][BUILD #1] CyanMobileX Compiled From Source [15/01/2013]

{
"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"
}
Welcome to the Cyanmobile eXperience
Hey there peeps, I compiled a new ROM for the HTC Sapphire -- CyanMobile!
It's made by the CyanMobile team, led by Squadzone.
Here's a short description (according to https://raw.github.com/CyanMobile/android_cyanmobile/gingerbread/Definitions.txt) with grammar edited by me:
What is CyanMobile?
CyanMobile is an aftermarket ROM like CyanogenMod, MIUI, JoyOS, LewaOS and others that are built from source. It is based on CyanogenMod 7 (Gingerbread v2.3.7) and uses modifications from AOSP and AOKP
Thanks To CyanogenMod Team, AOKP Team, and AOSP Team for Their Work
**********************************************************************************************************************
** CyanMobile is Short of " *Cyan* (CyanogenMod) *Mob* (Mobiling) *I* (Improving) and *L* (Let's) *E* (Experiment)" **
**********************************************************************************************************************
All features are based on what uses do and what users need with a lots of improvement here and there.
This ROM optimizes Gingerbread, but uses updates from other branchs (ICS stuff, AOSP and AOKP) with reverse engineering or backporting skill.
It can be used without needing to have any Google application installed....
Let us show you what is in CyanMobile:
====================================================================================================
1. Statusbar :
* Date
- Show/Hide Date
- Date Colour
* Notications
- Ticker Color
- No Title Color
- Latest Title Color
- Ongoing Title Color
- Clear Label Button Color
- Title Color
- Item Color
- Time Color
- Tile View [ Android 4.2 ]
* Icons
- Show/Hide Notification Icons
- Show/Hide Statusbar Icons
- Show/Hide Headset/Alarm/Bluetooth/Gps/Sync/Wifi/3G/4G Icon
* Clock
- 4 Clock styles (Right, Left, Center and Hide)
- Clock Color
- Clock Font Size
* Carrier label
- Show/Hide Carrier Label
- Bottom Carrier Label
- 3 Carrier Label On Statusbar Styles (Right, Left and Center)
- Carrier Label Color
- 4 Carrier Logo Styles (Right, Left, Center and Custom Logo)
* Signal
- 5 Different Styles (Bars, Text, Text w/dBm, text w/Auto Color and Hide)
- Wifi Signal Text
* Battery
- 7 Different Styles (Icon, Percentage, Top Statusbar, Side Bar, Behind Statusbar, Navigation Bar and Hide)
- 3 Different Battery Percentage Format (Default, Percentage and Full Color)
- Statusbar Battery Color
* Power Widget
- 4 Different Layouts (Default, Bottom, Grid and Tab)
- Music Widget
- Grid Layout Customizing
* Misc
- Refactor New Statusbar Layout
- Power Clock
- Power Date
- Weather PopUp
- Shortcut Button
- Show/Hide Statusbar
- Reverse Statusbar Icons And Layout
- Statusbar Brightness Control
- Statusbar Fonts Size
- Statusbar Icons Size
- Statusbar Height Size
- Statusbar Background
- Statusbar Background Color
- Notification Background
- Notification Background Color
====================================================================================================
2. Framework :
* Lockscreen
- 7 Different Lockscreen Styles (Sliding Tab, Rotary, Lense, Ring, Honeycomb (beta), Circular (alpha) , Sense (Beta) , Jellybean Glow (Beta) and Jellybean Pad (BETA) )
- Lockscreen Widget Color
- Sms/Call Notifications
- Fuzzy Clock
- Kanji Clock
- Custom Text Lockscreen
- Widget Layouts
- Pattern Styles
* Power Saver
- Screen Off Data Action
- Data Action Delay
- Sync Action
- Sync Time Interval
- Screen Off Wifi Action
- Sync Data Usage
- Mobile Data Preference
* Application
- Native A2SD Framework Core
- Installation Place
* Display
- Bravia Engine
- Rotation Animation
- Window Animations
- Transition Animations
- LCD Density
* Input
- Quick Key Behavior
- Enable/Disable Vibrate on Shutdown
- Explorer Key
* Power Menu
- Show/Hide Power menu/Silent/Airplane/Profile/Screenshot/Power saver/Hibernate/Suspend Toggles
* Fonts
- Change Fonts System
- Change Fonts Type
* OverScroll
- Effect
- Color
- Weight
* Core Replacer
- Change System Apk
- Change Framework Apk/Jar
* Boot/Shutdown animation and Sound
- Preview
- Change Bootanimation
- Change Shutdownanimation
- Change Bootsound
- Reset
* Misc
- New Notifications Design
- Intruder Alert is Life
- New Dialog Design
- Backported Some Apis From Jellybean
- Clear Market Data
- Global Text Color Change
- Global App Background Change
- Soft Button Statusbar
- Navigation Button Bar
- Choose Navi Button
- Navigation Button Bar Size
- Navigation Bar Background
- Extend Power Menu
- Remap Volume Keys
- Lock Volume Keys
- Volume Key Beeps
- Swap Volume Keys
- Task Switcher
====================================================================================================
3. Sound :
* Features
- Loop Ringtone
- Flip Down To Mute Ringer/Snooze Alarm
- Increasing Ringtone Volume
- Less Frequent Notification Sound
- Battery Full/Low Alert
- Charging Plug/Unplug Sound
====================================================================================================
4. Tethering :
* Features
- Bluetooth Tether
- Auto Usb Tether
====================================================================================================
5. Phone :
* Features
- Smart Phone Call
- Back Button To End Call
- Menu Button To Answer Call
- Reject Call with Message
- Allow Incall UI Touch
- Call Me Louder While Inside Bags
- Speed Dials
- Video As Ringtone
- Ring Delay
- Export/Import SIM Contacts
====================================================================================================
6. Messaging :
* Features
- Bubble/Black/Transparent Theme
- Smart Phone Call
- Hide Avatar
- Strip Unicode
- Emoji Support
- Convo List/Subject Font Size
- Sms Vibrate Morse
- Brutal Sender
- Sms PopUp
====================================================================================================
7. Music :
* Features
- Shake To Next/Prev/Play/Pause/Shuttle Track
- Favorite Folder
- Flip To Play/Pause
- Smooth Play Track
====================================================================================================
8. Locations :
* Features
- Enable/Disable Assisted GPS
- GPS Tracker Performance
- Security Device Finder
====================================================================================================
9. Performance :
* Features
- New I/O Scheduler Option
- New Dithering Support
- Enable Bootsound
- Bootsound Volume
- Enable Shutdownanimation
- Gmaps Hack
- KSM Settings
- Battery Polling
- Low Mem Killer Option
- Scrolling Option
- SD Read Ahead Size option
- Screen Off Max CPU Freq
====================================================================================================
10. Misc :
* Features
- ADWLauncher Improved
- Browser Improved
- Calculator Improved
- FM Radio Improved
- File Manager Updated
- SIM ToolKit Improved
- Screenshots Improved
- Task Manager
- Voice Dialer Improved
====================================================================================================
11. All Binary and Library is up to Date
====================================================================================================
That's it, other features not mentioned here came from CyanogenMod 7
Don't Use Any Scripts Like Link2SD, Bravia Hack, Xloud etc They Are Inbuilt !!
Click to expand...
Click to collapse
To Find OUT the features, YOU NEED TO PLAY AROUND WITH THE ROM xD
CyanMobile tries to improve all hardware functions and is always adding new features so it may have some bugs and requires user feedback to fix the bugs.
DONATION:
Donate to Keyur Maru
Donate to Squadzone
Check Next Post For What's Working ! and What's Not !

=======================
Cyan MoBiLe eXperiance
=======================
What's Working in it ? [ Hope so ]
-Network
-HW
-Audio
-Video
-Cam
-DAMM SMOOTH
-Sensors
What's Not Working ? [ Hope so ]
-You Need to Tell me xD
For Change Log Check Next Post

Change Log for Build #1 [16/01/13]
Initial Release for Sapphire
*****Please Read the Flashing Instructions !*****

Screenshots From Wildfire Buzz , LGE P500 And Galaxy Fit
This are From Other Devices Please Provide me From Sapphire Thank you !

DownLoadS
Current Version
Click to expand...
Click to collapse
update-CyanMobile-eXperience-DS-20130116-Release.zip
Click to expand...
Click to collapse
Click that image to start download of latest rom
Google Apps
Click me to Advance the Exploit [ Google APPS ]

***Important***​
How To Flash The Rom xD * IMPORTANT *
-Click Thanks , Rate The Thread And Press Newsworthy Thread ( OPTIONAL BUT * HIGHLY RECOMMENDED * )
-Download The Rom
-Wipe ALL
-Flash The Rom
-Reboot From Recovery
-Now Wait for 3-4 Minutes
-Rom Will Not Boot
-Now Remove Battery
-Reinsert Battery
-Now Start The Phone
-It will Boot up Now
-Enjoy The Rom

Hello,
CMX Users Now I had setted up CMX BuildBot !! Now you could always check status of the builds !!
Keep your eyes here : http://builder.pecancm.insomnia247.nl/job/CyanMobile-Builds/
It is Not Building Only for Sapphire It is Building LG P350 , LG P500 , HTC Buzz and More Devices to be added in future !!
DONATION:
Donate to Keyur Maru For Buying this Phone So I can Provide Further Updates
Donate to Sqadzone

I will be ur tester. sound like a good ROM.
could you include some pics or screen capture? thanks for your effort on our magic.

I want to test this rom. But I can't see link of the rom.

It is released

I have a HTC magic 32A device but I could not find rom for it.

hanntbk said:
I have a HTC magic 32A device but I could not find rom for it.
Click to expand...
Click to collapse
there is important information missing...
is this for 32A or 32B?
if it is for 32A, is it for old radio or new radio?
Thanks!

blizard80 said:
there is important information missing...
is this for 32A or 32B?
if it is for 32A, is it for old radio or new radio?
Thanks!
Click to expand...
Click to collapse
Is official cm7 for 32A or 32B !! it is same as cm7!

Cm7 is not officially available to sapphire.
So I can flash that file in either a 32A old radio or new radio? Has auto kernel?
I will test later.
Thank you!
Sent from my BlackBerry 9900 using Tapatalk

blizard80 said:
Cm7 is not officially available to sapphire.
So I can flash that file in either a 32A old radio or new radio? Has auto kernel?
I will test later.
Thank you!
Sent from my BlackBerry 9900 using Tapatalk
Click to expand...
Click to collapse
What the hell!!!! I compiled with mods to this device config it says it is for dream_sapphire https://github.com/CyanogenMod/android_device_htc_dream_sapphire
so this is not for this device ?

first, thanks for releasing this for the sapphire.
what i was saying is that CM7 is not supported by cyanogen as you see here:
http://get.cm/?device=dream_sapphire
there are differences in kernel for 32A and 32B... thats why i'm asking.
i can't test it right now but i will do it later and i will report.
thanks for this release.

blizard80 said:
first, thanks for releasing this for the sapphire.
what i was saying is that CM7 is not supported by cyanogen as you see here:
http://get.cm/?device=dream_sapphire
there are differences in kernel for 32A and 32B... thats why i'm asking.
i can't test it right now but i will do it later and i will report.
thanks for this release.
Click to expand...
Click to collapse
But i can see gingerbread tree here https://github.com/CyanogenMod/android_device_htc_dream_sapphire/tree/gingerbread
I don't know why cm is not releasing gb builds ? please someone test it and tell me results !!

I can not install ...
(status 7)
Instalation aborted
HTC Magic 32A Eng S-OFF

katurras said:
I can not install ...
(status 7)
Instalation aborted
HTC Magic 32A Eng S-OFF
Click to expand...
Click to collapse
If you can flash CM7 you should be able to flash this!

katurras said:
I can not install ...
(status 7)
Instalation aborted
HTC Magic 32A Eng S-OFF
Click to expand...
Click to collapse
What hboot and/or radio?
I get that error, but updated the hboot and radio et voila!
It works
BTW I installed the hboot and radio from here
PD: I flashed the ROM but it does not boot.
I get many errors.....
D/AndroidRuntime( 145): >>>>>> AndroidRuntime START com.android.internal.os.Zyg
oteInit <<<<<<
I/AndroidRuntime( 145): Heap size: -Xmx16m
D/AndroidRuntime( 145): CheckJNI is OFF
W/dalvikvm( 145): Exception Ljava/util/regex/PatternSyntaxException; thrown whi
le initializing Landroid/graphics/Rect;
I/dalvikvm( 145): Rejecting re-init on previously-failed class Landroid/graphic
s/Rect; v=0x0
E/dalvikvm( 145): Class lookup Ljava/lang/NoClassDefFoundError; attempted while
exception Ljava/lang/ExceptionInInitializerError; pending
I/dalvikvm( 145): DALVIK THREADS:
I/dalvikvm( 145): (mutexes: tll=0 tsl=0 tscl=0 ghl=0 hwl=0 hwll=0)
I/dalvikvm( 145): "main" prio=5 tid=1 RUNNABLE
I/dalvikvm( 145): | group="main" sCount=0 dsCount=0 obj=0x40196198 self=0xce4
0
I/dalvikvm( 145): | sysTid=145 nice=0 sched=0/0 cgrp=default handle=-13450024
00
I/dalvikvm( 145): at dalvik.system.NativeStart.main(Native Method)
I/dalvikvm( 145): at dalvik.system.NativeStart.main(Native Method)
I/dalvikvm( 145):
E/dalvikvm( 145): VM aborting
I/DEBUG ( 79): *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *
**
I/DEBUG ( 79): Build fingerprint: 'tmobile/opal/sapphire/sapphire:2.2.1/FRG8
3/60505:user/release-keys'
I/DEBUG ( 79): pid: 145, tid: 145 >>> zygote <<<
I/DEBUG ( 79): signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr deadd00
d
I/DEBUG ( 79): r0 fffffec4 r1 deadd00d r2 00000026 r3 00000000
I/DEBUG ( 79): r4 aca9e5c0 r5 0000ce40 r6 aca9e5c0 r7 00000000
I/DEBUG ( 79): r8 00000000 r9 00000000 10 00000000 fp 00000000
I/DEBUG ( 79): ip aca9e720 sp bef529d0 lr afd19919 pc aca3fb66 cpsr 200
00030
I/DEBUG ( 79): #00 pc 0003fb66 /system/lib/libdvm.so (dvmAbort)
I/DEBUG ( 79): #01 pc 00064a52 /system/lib/libdvm.so
I/DEBUG ( 79): #02 pc 00064cee /system/lib/libdvm.so (dvmFindSyst
emClassNoInit)
I/DEBUG ( 79): #03 pc 00064d06 /system/lib/libdvm.so (dvmFindSyst
emClass)
I/DEBUG ( 79): #04 pc 0003f2ba /system/lib/libdvm.so (dvmThrowCha
inedException)
I/DEBUG ( 79): #05 pc 0003f31c /system/lib/libdvm.so (dvmThrowCha
inedExceptionWithClassMessage)
I/DEBUG ( 79): #06 pc 000628d4 /system/lib/libdvm.so
I/DEBUG ( 79): #07 pc 0006476a /system/lib/libdvm.so (dvmInitClas
s)
I/DEBUG ( 79): #08 pc 00046e2c /system/lib/libdvm.so
I/DEBUG ( 79): #09 pc 000585e8 /system/lib/libandroid_runtime.so
I/DEBUG ( 79): #10 pc 0005863a /system/lib/libandroid_runtime.so
(_Z34register_android_graphics_GraphicsP7_JNIEnv)
I/DEBUG ( 79): #11 pc 000357f6 /system/lib/libandroid_runtime.so
I/DEBUG ( 79): #12 pc 0003582c /system/lib/libandroid_runtime.so
(_ZN7android14AndroidRuntime8startRegEP7_JNIEnv)
I/DEBUG ( 79): #13 pc 000358f6 /system/lib/libandroid_runtime.so
(_ZN7android14AndroidRuntime5startEPKcb)
I/DEBUG ( 79): #14 pc 00008ca2 /system/bin/app_process
I/DEBUG ( 79): #15 pc 000153e0 /system/lib/libc.so (__libc_init)
I/DEBUG ( 79):
I/DEBUG ( 79): code around pc:
I/DEBUG ( 79): aca3fb44 2006447a ecc8f7d1 20004c09 edf0f7d1
I/DEBUG ( 79): aca3fb54 447c4808 6bdb5823 d0002b00 49064798
I/DEBUG ( 79): aca3fb64 700a2226 ee5cf7d1 000435c5 00045183
I/DEBUG ( 79): aca3fb74 0005ea66 fffffec4 deadd00d b510b40e
I/DEBUG ( 79): aca3fb84 4c0a4b09 b083447b aa05591b ca026b5b
I/DEBUG ( 79):
I/DEBUG ( 79): code around lr:
I/DEBUG ( 79): afd198f8 447b4a0d 589cb083 90012600 686768a5
I/DEBUG ( 79): afd19908 220ce008 2b005eab 1c28d003 47889901
I/DEBUG ( 79): afd19918 35544306 d5f43f01 2c006824 b003d1ee
I/DEBUG ( 79): afd19928 bdf01c30 00028c26 ffffff88 1c0fb5f0
I/DEBUG ( 79): afd19938 b0871c3d a9044355 1c16ac01 604d9004
I/DEBUG ( 79):
I/DEBUG ( 79): stack:
I/DEBUG ( 79): bef52990 00000000
I/DEBUG ( 79): bef52994 00000000
I/DEBUG ( 79): bef52998 afd4372c
I/DEBUG ( 79): bef5299c afd436d8
I/DEBUG ( 79): bef529a0 00000000
I/DEBUG ( 79): bef529a4 afd19919 /system/lib/libc.so
I/DEBUG ( 79): bef529a8 00000000
I/DEBUG ( 79): bef529ac afd18985 /system/lib/libc.so
I/DEBUG ( 79): bef529b0 00000000
I/DEBUG ( 79): bef529b4 0005ea66
I/DEBUG ( 79): bef529b8 0000ce40
I/DEBUG ( 79): bef529bc aca9e5c0
I/DEBUG ( 79): bef529c0 00000000
I/DEBUG ( 79): bef529c4 afd189e3 /system/lib/libc.so
I/DEBUG ( 79): bef529c8 df002777
I/DEBUG ( 79): bef529cc e3a070ad
I/DEBUG ( 79): #00 bef529d0 aca85ffb /system/lib/libdvm.so
I/DEBUG ( 79): bef529d4 aca64a57 /system/lib/libdvm.so
I/DEBUG ( 79): #01 bef529d8 41d1dd8d
I/DEBUG ( 79): bef529dc 41d5b7db
I/DEBUG ( 79): bef529e0 00080f40
I/DEBUG ( 79): bef529e4 aca85ffb /system/lib/libdvm.so
I/DEBUG ( 79): bef529e8 000001b4
I/DEBUG ( 79): bef529ec 00000000
I/DEBUG ( 79): bef529f0 00000000
I/DEBUG ( 79): bef529f4 00000000
I/DEBUG ( 79): bef529f8 00000000
I/DEBUG ( 79): bef529fc aca85ffb /system/lib/libdvm.so
I/DEBUG ( 79): bef52a00 00080f40
I/DEBUG ( 79): bef52a04 00000000
I/DEBUG ( 79): bef52a08 0000ce40
I/DEBUG ( 79): bef52a0c aca64cf3 /system/lib/libdvm.so
I/ServiceManager( 76): service 'media.camera' died
I/ServiceManager( 76): service 'media.audio_policy' died
I/ServiceManager( 76): service 'media.audio_flinger' died
I/ServiceManager( 76): service 'media.player' died
I/Netd ( 147): Netd 1.0 starting
I/ ( 146): ServiceManager: 0xad50
I/HTC Acoustic( 146): libhtc_acoustic.so version 1.0.1.1.
E/HTC Acoustic( 146): Fail to open /system/etc/AudioPara_VODA-Spain.csv -1.
E/HTC Acoustic( 146): Fail to open /system/etc/AudioPara4.csv -1.
E/HTC Acoustic( 146): read audio para from file failed -1
E/AudioHardwareMSM72XX( 146): Could not set acoustic parameters to share memory
: -1
D/AudioHardwareMSM72XX( 146): mNumSndEndpoints = 13
D/AudioHardwareMSM72XX( 146): BT MATCH HANDSET
D/AudioHardwareMSM72XX( 146): BT MATCH SPEAKER
D/AudioHardwareMSM72XX( 146): BT MATCH HEADSET
D/AudioHardwareMSM72XX( 146): BT MATCH BT
D/AudioHardwareMSM72XX( 146): BT MATCH CARKIT
D/AudioHardwareMSM72XX( 146): BT MATCH TTY_FULL
D/AudioHardwareMSM72XX( 146): BT MATCH TTY_VCO
D/AudioHardwareMSM72XX( 146): BT MATCH TTY_HCO
D/AudioHardwareMSM72XX( 146): BT MATCH NO_MIC_HEADSET
D/AudioHardwareMSM72XX( 146): BT MATCH FM_HEADSET
D/AudioHardwareMSM72XX( 146): BT MATCH HEADSET_AND_SPEAKER
D/AudioHardwareMSM72XX( 146): BT MATCH FM_SPEAKER
D/AudioHardwareMSM72XX( 146): BT MATCH CURRENT
D/AudioHardwareInterface( 146): setMode(NORMAL)

Proximity Sensor issues.

Hey guys. Recently I have been wondering what's going on with.my Sensor. It used to work just fine until I started flashing new Roms. I had the sensor working on the default.CM 9.1.0 rom and I can't remember another rom it worked with. I now have ViperS 1.6.3 for Sensation. I love this rom, but I checked AndroSensor and the status for the ProxSensor always says "Waiting for event" I am not sure what to do here, my sensor just doesn't work anymore! Troubleshooting ideas please!
Sent from Ty's ViperS Sensation. A beast of a phone.

ClipTy said:
Hey guys. Recently I have been wondering what's going on with.my Sensor. It used to work just fine until I started flashing new Roms. I had the sensor working on the default.CM 9.1.0 rom and I can't remember another rom it worked with. I now have ViperS 1.6.3 for Sensation. I love this rom, but I checked AndroSensor and the status for the ProxSensor always says "Waiting for event" I am not sure what to do here, my sensor just doesn't work anymore! Troubleshooting ideas please!
Sent from Ty's ViperS Sensation. A beast of a phone.
Click to expand...
Click to collapse
Does the screen automatically turnoff when you take it close to your face on call....if so your proximity sensor is working...
Also there should be no issues in the sensor bcoz of VIperS rom....but if issue persists, full wipe and flash again.

I might need to full wipe.
Sent from Ty's ViperS Sensation. A beast of a phone.

murtazasamiwala said:
Does the screen automatically turnoff when you take it close to your face on call....if so your proximity sensor is working...
Also there should be no issues in the sensor bcoz of VIperS rom....but if issue persists, full wipe and flash again.
Click to expand...
Click to collapse
So I did a full wipe, flashed a clean ViperS rom, and I still get nothing. Went back to my previous back up.
I have been reading all over the place and tons of people never even found a solution for said issues. I'm going to ask on the Viper thread.

Any ideas? Cmon. Someone has to know.
Sent from Ty's ViperS Sensation. A beast of a phone.

Still searching the problem at here : http://forum.xda-developers.com/showthread.php?p=42735640#post42735640

teeebor said:
Still searching the problem at here : http://forum.xda-developers.com/showthread.php?p=42735640#post42735640
Click to expand...
Click to collapse
I have the same problem till Saturday. But I cannot post in the development thread and help to fix the problem.

x2ht1 said:
I have the same problem till Saturday. But I cannot post in the development thread and help to fix the problem.
Click to expand...
Click to collapse
Ok,
First check this directory: /sys/devices/virtual/optical_sensors
If it does not exist, you have the same problem. But if the folder exist, just wipe the cache and dalvik

No don't have this folder, too.
Till yesterday I have tried a several things.
First my Rom is Dark Sense 3.6, Sultan kernel from DS Store revision15 office version, Firmware 3.33 with Patch to HBoot 1.29.
1. I have tried a another kernel, didn't help.
2. Install a nandroid, didn't help.
3. Do a full wipe and install the Dark Sense Rom again, and didn't help.
4. Copie the scripts from the other thread (01lightsensor..e.g.) to the init.d folder, didn't help.
5. Then I tried to copy the optical_sensors Folder directly to sys/devices/virtual and then I get an error! "There is not enough space" (0Bit Free). Mhhh..that's not normal. I have root and read write access!
6. I tried a CW10.1 Rom and it work, till after a reboot.
Now I have install my nandroid and the issues still exist. I don't want to change my Rom, I like it.
Hope my post helps to solve the problem.

Yesterday I decided to change my Rom to CM10.1 from Albinoman...
The sensors works with this Rom! After some testing time I come to the result: that's not my rom. The camera is really bad against the HQCamera 1.5.
There is no Beats Audio, Sony xLoud and Bravia Engine 2.
...I make a full wipe again
Install my nandroid and the sensors still work
But I don't make a reboot. I thing after a reboot the sensor stops to work...

So you find our biggest problem. We can't figure out why is this happening. Sometimes after wipe it works, sometimes other firmwares work and sometimes RUU or Rom change work. There must be a bug in the boot, and don't know yet how to fix it :/
Anyway thanks for reply
Sent from my HTC Sensation Z710e using xda premium

teeebor said:
So you find our biggest problem. We can't figure out why is this happening. Sometimes after wipe it works, sometimes other firmwares work and sometimes RUU or Rom change work. There must be a bug in the boot, and don't know yet how to fix it :/
Click to expand...
Click to collapse
I thing the space is not the problem. It´s a virtual folder.
Now I can say Rom with Sense don´t work..
I have try a many roms (Elegancia, Dark Forest, DarkSense and the Stock ICS ROM 3.33.401.106). The sensors don´t work whith any of these
rom´s.
With other roms like CM9, CM10.1 or HyperSensation it works without issues...
I can post some pictures from my bootscreen log where you can see the error!

here is the pic
View attachment 2059400

I see it returns 0, but why? When it fails it must return a specific error code exept zero.
So in CM all optical sensors must work? Hmm i try it, but my preferred Launcher is Roise because Beats audio and GUI
Tomorrow i will share the result

teeebor said:
I see it returns 0, but why? When it fails it must return a specific error code exept zero.
So in CM all optical sensors must work? Hmm i try it, but my preferred Launcher is Roise because Beats audio and GUI
Tomorrow i will share the result
Click to expand...
Click to collapse
your right! normally there are the values from the light and proximity sensor. you see an errorcode he is at the line above.
smd_tty_open: DS open failed -19
Click to expand...
Click to collapse
The line isn´t ther when the sensors work! I thing he couldn´t open the driver, but why?
the app for the loading screen called "live dmesg lite"

x2ht1 said:
your right! normally there are the values from the light and proximity sensor. you see an errorcode he is at the line above.
The line isn´t ther when the sensors work! I thing he couldn´t open the driver, but why?
the app for the loading screen called "live dmesg lite"
Click to expand...
Click to collapse
It could not be a permission problem cause i fixed it. Maybe a malfunctioning driver that leave behind something that block the sensor's driver.I don't have a better idea.

CM doesn't help. But somehow I could get it to work.
Here is the log when the sensors failed to start:
{
"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"
}
And when it worked:
edit
The columns are the following: Type - Sender - PID - Message

Till yesterday my sensor work, too. but he restarts every time.
D/SensorService( 2473): enable: get sensor name = MPL accel
D/Sensors ( 2473): handle : 4 en: 1, v010.0 - Try to resolve lock issue
D/Sensors ( 2473): lock_status = 63
D/Sensors ( 2473): Andy: MPLSensor::enable: lock1
D/Sensors ( 2473): mEnabled = 0x10
D/Sensors ( 2473): set_power_states++: enabled_sensors: 16 dmp_started: 0
D/Sensors ( 2473): Before if statment: cs:0 rs:1 en_ped:0 da_ped:0 en_g:0 da_g:0
D/Sensors ( 2473): STOP timerirq_1
D/Sensors ( 2473): Starting DMP
I/ ( 2473): mpu3050_resume: Resuming to 0070
D/Sensors ( 2473): Exit: Starting DMP
D/Sensors ( 2473): set_power_states--
D/Sensors ( 2473): Andy: MPLSensor::enable: unlock1
D/Sensors ( 2473): MPLSensor::enable--1
D/Sensors ( 2473): (llu)G_Delay = 200
I/ ( 2473): mpu3050_resume: Resuming to 0070
I/ ( 2473): mpu3050_suspend: suspending sensors to 0070
I/ ( 2473): mpu3050_suspend: Will resume next to 0070
I/MPL-ml ( 2473): Actual ODR: 25 Hz
D/SensorService( 2473): SensorDevice::activate--: handle = 0x4, enabled = 0x1
D/SensorService( 2473): pid=29490, uid=10176
D/Sensors ( 2473): (llu)G_Delay = 20
I/ ( 2473): mpu3050_resume: Resuming to 0070
I/ ( 2473): mpu3050_suspend: suspending sensors to 0070
I/ ( 2473): mpu3050_suspend: Will resume next to 0070
I/MPL-ml ( 2473): Actual ODR: 25 Hz
D/SensorService( 2473): disable: get sensor name = MPL accel
D/Sensors ( 2473): handle : 4 en: 0, v010.0 - Try to resolve lock issue
D/Sensors ( 2473): lock_status = 4
D/Sensors ( 2473): Andy: MPLSensor::enable: lock1
W/MPL-sup ( 2473): MLGetAKMComassStatus, gAKMCompassStatus = 0
D/Sensors ( 2473): mEnabled = 0x0
D/Sensors ( 2473): set_power_states++: enabled_sensors: 0 dmp_started: 1
D/Sensors ( 2473): Before if statment: cs:0 rs:0 en_ped:0 da_ped:0 en_g:0 da_g:0
D/Sensors ( 2473): Stopping DMP
I/ ( 2473): mpu3050_suspend: suspending sensors to 0000
I/ ( 2473): mpu3050_suspend: Will resume next to 0070
D/Sensors ( 2473): inside if(s_use_timerirq)
D/Sensors ( 2473): set_power_states--
D/Sensors ( 2473): Andy: MPLSensor::enable: unlock1
D/Sensors ( 2473): MPLSensor::enable--1
D/SensorService( 2473): SensorDevice::activate--: handle = 0x4, enabled = 0x0
D/SensorService( 2473): pid=29490, uid=10176
Click to expand...
Click to collapse

after a week i can say that my sensors still work but sometimes the drivers restarts and then the sensors didn´t work.

The sensors still not working for me, but several days ago the proximity sensor lights up in red

[S4][DEVs only] Zoe development

Using this mod: http://forum.xda-developers.com/showthread.php?t=2436347
we are currently stuck here (no front camera and zoom bug), enabling front camera we got this:
Code:
[COLOR="Red"]E/ ( 274): [AWB Calibration] read fuse ID fail
E/mm-camera( 274): [sensor_getVersion] get version fail
E/mm-camera( 274): MCTL_COMPID_ACTUATOR handle is NULL[/COLOR]
E/QCameraHWI_Parm( 260): Video HDR mode is not supported for this sensor
W/QCameraHWI_Parm( 260): setVideoMode is not supported if PHOTO MODE
W/QCameraHWI_Parm( 260): setVideoMode is not supported if PHOTO MODE
W/QCameraHWI_Parm( 260): android::status_t android::QCameraHardwareInterface::captureModeInitConfig(): other capture mode 1
D/Vold ( 245): Receive camera burst event
E/mm-camera( 274): MCTL_COMPID_ACTUATOR handle is NULL
W/S_CameraController( 4045): OIS is not supported.
W/S_CameraController( 4045): Video slow motion is not supported.
W/S_CameraController( 4045): Video Stabilization is not supported.
W/S_CameraController( 4045): Video 720p 60fps is not supported.
W/S_CameraController( 4045): Video HDR is not supported.
W/S_CameraController( 4045): Photo HDR is not supported.
E/S_CameraController( 4045): SupportedList.FlashMode == null
W/S_ZoeController( 4045): exitZoeMode() - Zoe mode is not entered
D/Property( 4045): [ICaptureResolutionManager.PhotoResolution] PHOTO_16_9_3264x1840(3264x1840) -> PHOTO_4_3_640x480(640x480)
D/Property( 4045): [ICaptureResolutionManager.VideoResolution] QHD(960x544) -> VGA(640x480)
E/S_CameraController( 4045): not support FlashMode !!
E/QCameraHWI_Parm( 260): Video HDR mode is not supported for this sensor
W/QCameraHWI_Parm( 260): setVideoMode is not supported if PHOTO MODE
W/QCameraHWI_Parm( 260): setVideoMode is not supported if PHOTO MODE
W/QCameraHWI_Parm( 260): android::status_t android::QCameraHardwareInterface::captureModeInitConfig(): other capture mode 1
[COLOR="Red"]E/QCameraHWI_Parm( 260): android::status_t android::QCameraHardwareInterface::setFocusMode(const android::CameraParameters&):Could not look up str value
E/QCameraHWI_Parm( 260): Invalid focus mode value: continuous-picture[/COLOR] [COLOR="Blue"]-> need framework fix, but it's not a big problem[/COLOR]
E/QCameraHWI_Parm( 260): android::status_t android::QCameraHardwareInterface::setParameters(const android::CameraParameters&): 2171, rc = -22
D/Vold ( 245): Receive camera burst event
[COLOR="Red"]E/mm-camera( 274): MCTL_COMPID_ACTUATOR handle is NULL
E/S_CameraController( 4045): setParameters exception[/COLOR] [COLOR="Blue"]-> it should be important[/COLOR]
E/mm-camera( 274): camif_client_set_params: camif has associated with obj mask 0x1
E/mm-camera( 274): config_MSG_ID_RESET_ACK CAMIF_PARAMS_ADD_OBJ_ID failed -1
[COLOR="Red"]F/libc ( 274): Fatal signal 11 (SIGSEGV) at 0x00000000 (code=1), thread 4116 (mm-qcamera-daem)[/COLOR][COLOR="Blue"] -> i think it's crashing because of other problems[/COLOR]
I/DEBUG ( 257): debuggerd: 2013-09-20 03:00:40
I/DEBUG ( 257): *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
I/DEBUG ( 257): Build fingerprint: 'htc/htc_europe/ville:4.2.2/JDQ39/240250.1:user/release-keys'
I/DEBUG ( 257): Revision: '3'
I/DEBUG ( 257): pid: 274, tid: 4116, name: mm-qcamera-daem >>> /system/bin/mm-qcamera-daemon <<<
....
I/DEBUG ( 257): backtrace:
I/DEBUG ( 257): #00 pc 00000000 <unknown>
I/DEBUG ( 257): #01 pc 0005ce0d /system/lib/liboemcamera.so
I/DEBUG ( 257): #02 pc 0002484d /system/lib/liboemcamera.so
I/DEBUG ( 257): #03 pc 0000e4b8 /system/lib/libc.so (__thread_entry+72)
I/DEBUG ( 257): #04 pc 0000dba4 /system/lib/libc.so (pthread_create+160)
I/DEBUG ( 257):
I/DEBUG ( 257): stack:
I/DEBUG ( 257): 4078e800 0003eed4
I/DEBUG ( 257): 4078e804 4043ce21 /system/lib/liboemcamera.so (vfe_config_mode+732)
I/DEBUG ( 257): 4078e808 00000005
I/DEBUG ( 257): 4078e80c 404a32c0
I/DEBUG ( 257): 4078e810 00000001
I/DEBUG ( 257): 4078e814 4078e88c [stack:4116]
I/DEBUG ( 257): 4078e818 00000000
I/DEBUG ( 257): 4078e81c 407b738c [stack:4116]
I/DEBUG ( 257): 4078e820 40436179 /system/lib/liboemcamera.so
I/DEBUG ( 257): 4078e824 4043909d /system/lib/liboemcamera.so
I/DEBUG ( 257): 4078e828 40438e7d /system/lib/liboemcamera.so
...
[COLOR="Red"]E/mm-camera( 4144): qcamsvr_load_gesture_lib Error opening gesture library
E/mm-camera( 4144): Cannot init Gesture library[/COLOR] [COLOR="Blue"]-> missing libs? not a big problem btw[/COLOR]
W/S_OperationTimeoutController( 4045): [Timeout] Name : Start preview
W/S_OperationTimeoutController( 4045): [Timeout] Start time : 1379638840004
W/S_OperationTimeoutController( 4045): [Timeout] Timeout : 5000
W/S_OperationTimeoutController( 4045): [Timeout] Call-back executor : [email protected]
W/S_HTCCamera( 4045): notifyCameraThreadBlocked(BlockedInCameraDriver)
W/S_HTCCamera( 4045): onCameraThreadBlocked(BlockedInCameraDriver)
W/S_AutoFocusController( 4045): unlockAutoFocus() - Null handle
W/S_ImageSettingsController( 4045): unlockAutoExposure() - Null handle
W/S_ImageSettingsController( 4045): unlockAutoWhiteBalance() - Null handle
W/S_HTCCamera( 4045): onPause() - mIsUIReady = false
W/AudioService( 920): stream was not muted by this client
E/AudioService( 920): Could not get client death handler for stream: 5
W/S_HTCCamera( 4045): onPause mIdle is false
W/S_HTCCamera( 4045): OnPause - Freeze UI !!!
W/S_HTCCamera( 4045): doOnPause() - start
W/S_HTCCamera( 4045): stopAccelerometer() - isAccelerometerStarted = false
W/S_HTCCamera( 4045): OnPause - hide UI, set mMainLayout invisible
W/S_HTCCamera( 4045): doOnPause() - end
[COLOR="Red"]E/mm-libcamera2( 260): mm_camera_stream_fsm_reg: ioctl VIDIOC_STREAMON failed: rc=-1
E/mm-libcamera2( 260): mm_camera_ch_fn: Failed in STREAM ON
E/mm-libcamera2( 260): mm_camera_action_start: rc=-1[/COLOR] [COLOR="Blue"]-> very important[/COLOR]
E/QCameraHWI_Still( 260): android::status_t android::QCameraStream_Snapshot::startStreamZSL(): Failure starting ZSL stream
[COLOR="Red"]E/mm-camera( 4144): qcamsvr_find_mctl_inst: no match for mctl_id = 1
E/mm-camera( 4144): qcamsvr_process_server_node_event: MSM_V4L2_* - cannot find mctl, id = 1[/COLOR] [COLOR="Blue"]-> it should be important[/COLOR]
is there a dev that already encountered this problem, and can help us?
@ImagioX1 @E.Cadro @olvrick @Turge @Zarboz

pirlano said:
Using this mod: http://forum.xda-developers.com/showthread.php?t=2436347
we are currently stuck here (no front camera and zoom bug), enabling front camera we got this:
Code:
[COLOR="Red"]E/ ( 274): [AWB Calibration] read fuse ID fail
E/mm-camera( 274): [sensor_getVersion] get version fail
E/mm-camera( 274): MCTL_COMPID_ACTUATOR handle is NULL[/COLOR]
E/QCameraHWI_Parm( 260): Video HDR mode is not supported for this sensor
W/QCameraHWI_Parm( 260): setVideoMode is not supported if PHOTO MODE
W/QCameraHWI_Parm( 260): setVideoMode is not supported if PHOTO MODE
W/QCameraHWI_Parm( 260): android::status_t android::QCameraHardwareInterface::captureModeInitConfig(): other capture mode 1
D/Vold ( 245): Receive camera burst event
E/mm-camera( 274): MCTL_COMPID_ACTUATOR handle is NULL
W/S_CameraController( 4045): OIS is not supported.
W/S_CameraController( 4045): Video slow motion is not supported.
W/S_CameraController( 4045): Video Stabilization is not supported.
W/S_CameraController( 4045): Video 720p 60fps is not supported.
W/S_CameraController( 4045): Video HDR is not supported.
W/S_CameraController( 4045): Photo HDR is not supported.
E/S_CameraController( 4045): SupportedList.FlashMode == null
W/S_ZoeController( 4045): exitZoeMode() - Zoe mode is not entered
D/Property( 4045): [ICaptureResolutionManager.PhotoResolution] PHOTO_16_9_3264x1840(3264x1840) -> PHOTO_4_3_640x480(640x480)
D/Property( 4045): [ICaptureResolutionManager.VideoResolution] QHD(960x544) -> VGA(640x480)
E/S_CameraController( 4045): not support FlashMode !!
E/QCameraHWI_Parm( 260): Video HDR mode is not supported for this sensor
W/QCameraHWI_Parm( 260): setVideoMode is not supported if PHOTO MODE
W/QCameraHWI_Parm( 260): setVideoMode is not supported if PHOTO MODE
W/QCameraHWI_Parm( 260): android::status_t android::QCameraHardwareInterface::captureModeInitConfig(): other capture mode 1
[COLOR="Red"]E/QCameraHWI_Parm( 260): android::status_t android::QCameraHardwareInterface::setFocusMode(const android::CameraParameters&):Could not look up str value
E/QCameraHWI_Parm( 260): Invalid focus mode value: continuous-picture[/COLOR] [COLOR="Blue"]-> need framework fix, but it's not a big problem[/COLOR]
E/QCameraHWI_Parm( 260): android::status_t android::QCameraHardwareInterface::setParameters(const android::CameraParameters&): 2171, rc = -22
D/Vold ( 245): Receive camera burst event
[COLOR="Red"]E/mm-camera( 274): MCTL_COMPID_ACTUATOR handle is NULL
E/S_CameraController( 4045): setParameters exception[/COLOR] [COLOR="Blue"]-> it should be important[/COLOR]
E/mm-camera( 274): camif_client_set_params: camif has associated with obj mask 0x1
E/mm-camera( 274): config_MSG_ID_RESET_ACK CAMIF_PARAMS_ADD_OBJ_ID failed -1
[COLOR="Red"]F/libc ( 274): Fatal signal 11 (SIGSEGV) at 0x00000000 (code=1), thread 4116 (mm-qcamera-daem)[/COLOR][COLOR="Blue"] -> i think it's crashing because of other problems[/COLOR]
I/DEBUG ( 257): debuggerd: 2013-09-20 03:00:40
I/DEBUG ( 257): *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
I/DEBUG ( 257): Build fingerprint: 'htc/htc_europe/ville:4.2.2/JDQ39/240250.1:user/release-keys'
I/DEBUG ( 257): Revision: '3'
I/DEBUG ( 257): pid: 274, tid: 4116, name: mm-qcamera-daem >>> /system/bin/mm-qcamera-daemon <<<
....
I/DEBUG ( 257): backtrace:
I/DEBUG ( 257): #00 pc 00000000 <unknown>
I/DEBUG ( 257): #01 pc 0005ce0d /system/lib/liboemcamera.so
I/DEBUG ( 257): #02 pc 0002484d /system/lib/liboemcamera.so
I/DEBUG ( 257): #03 pc 0000e4b8 /system/lib/libc.so (__thread_entry+72)
I/DEBUG ( 257): #04 pc 0000dba4 /system/lib/libc.so (pthread_create+160)
I/DEBUG ( 257):
I/DEBUG ( 257): stack:
I/DEBUG ( 257): 4078e800 0003eed4
I/DEBUG ( 257): 4078e804 4043ce21 /system/lib/liboemcamera.so (vfe_config_mode+732)
I/DEBUG ( 257): 4078e808 00000005
I/DEBUG ( 257): 4078e80c 404a32c0
I/DEBUG ( 257): 4078e810 00000001
I/DEBUG ( 257): 4078e814 4078e88c [stack:4116]
I/DEBUG ( 257): 4078e818 00000000
I/DEBUG ( 257): 4078e81c 407b738c [stack:4116]
I/DEBUG ( 257): 4078e820 40436179 /system/lib/liboemcamera.so
I/DEBUG ( 257): 4078e824 4043909d /system/lib/liboemcamera.so
I/DEBUG ( 257): 4078e828 40438e7d /system/lib/liboemcamera.so
...
[COLOR="Red"]E/mm-camera( 4144): qcamsvr_load_gesture_lib Error opening gesture library
E/mm-camera( 4144): Cannot init Gesture library[/COLOR] [COLOR="Blue"]-> missing libs? not a big problem btw[/COLOR]
W/S_OperationTimeoutController( 4045): [Timeout] Name : Start preview
W/S_OperationTimeoutController( 4045): [Timeout] Start time : 1379638840004
W/S_OperationTimeoutController( 4045): [Timeout] Timeout : 5000
W/S_OperationTimeoutController( 4045): [Timeout] Call-back executor : [email protected]
W/S_HTCCamera( 4045): notifyCameraThreadBlocked(BlockedInCameraDriver)
W/S_HTCCamera( 4045): onCameraThreadBlocked(BlockedInCameraDriver)
W/S_AutoFocusController( 4045): unlockAutoFocus() - Null handle
W/S_ImageSettingsController( 4045): unlockAutoExposure() - Null handle
W/S_ImageSettingsController( 4045): unlockAutoWhiteBalance() - Null handle
W/S_HTCCamera( 4045): onPause() - mIsUIReady = false
W/AudioService( 920): stream was not muted by this client
E/AudioService( 920): Could not get client death handler for stream: 5
W/S_HTCCamera( 4045): onPause mIdle is false
W/S_HTCCamera( 4045): OnPause - Freeze UI !!!
W/S_HTCCamera( 4045): doOnPause() - start
W/S_HTCCamera( 4045): stopAccelerometer() - isAccelerometerStarted = false
W/S_HTCCamera( 4045): OnPause - hide UI, set mMainLayout invisible
W/S_HTCCamera( 4045): doOnPause() - end
[COLOR="Red"]E/mm-libcamera2( 260): mm_camera_stream_fsm_reg: ioctl VIDIOC_STREAMON failed: rc=-1
E/mm-libcamera2( 260): mm_camera_ch_fn: Failed in STREAM ON
E/mm-libcamera2( 260): mm_camera_action_start: rc=-1[/COLOR] [COLOR="Blue"]-> i don't think it's too much important[/COLOR]
E/QCameraHWI_Still( 260): android::status_t android::QCameraStream_Snapshot::startStreamZSL(): Failure starting ZSL stream
[COLOR="Red"]E/mm-camera( 4144): qcamsvr_find_mctl_inst: no match for mctl_id = 1
E/mm-camera( 4144): qcamsvr_process_server_node_event: MSM_V4L2_* - cannot find mctl, id = 1[/COLOR] [COLOR="Blue"]-> it should be important[/COLOR]
is there a dev that already encountered this problem, and can help us?
@ImagioX1 @E.Cadro @olvrick @Turge @Zarboz
Click to expand...
Click to collapse
grep is your friend
MCTL_COMPID_ACTUATOR

Zarboz said:
grep is your friend
MCTL_COMPID_ACTUATOR
Click to expand...
Click to collapse
i know, the problem is in liboemcamera.so, mctl_init & sensor_init are changed, and i'm looking at this
i was just asking if One XL devs already solved this problem in the past or not, or if you have some hints
In One S liboemcamera there is one only "MCTL_COMPID_ACTUATOR handle is NULL" reference:
.rodata:000BBAEA aMctl_compid__0 DCB "MCTL_COMPID_ACTUATOR handle is NULL",0xA,0
In One liboemcamera there are three reference:
.rodata:000AAB54 aMctl_compid_ac DCB "MCTL_COMPID_ACTUATOR handle is NULL",0xA,0 ; DATA XREF: sub_1F240+A64o
.rodata:000C650C aSMctl_compid_0 DCB "%s MCTL_COMPID_ACTUATOR handle is NULL",0xA,0
.rodata:000C7EF4 aSMctl_compid_2 DCB "%s: MCTL_COMPID_ACTUATOR handle is NULL",0xA,0
the one causing the error is the first
in dmesg, error happens beetween this two lines:
<6>[ 141.009064] c1 4731 [CAM] mt9v113_ioctl, cfgtype = 10
(reached with original cam and zoe mod)
it's in drivers/media/video/msm/sensor/mt9v113_v4l2.c
function: int mt9v113_sensor_config(void __user *argp)
<6>[ 141.009430] c1 4731 [CAM] vfe32_proc_general: cmdID = START
(start is not reached with Zoe mod)
it's in drivers/media/video/msm/vfe/msm_vfe32.c
function: static int vfe32_proc_general(
struct msm_cam_media_controller *pmctl,
struct msm_isp_cmd *cmd,
struct vfe32_ctrl_type *vfe32_ctrl)

Will be great to be ported this feature and new [ROM] MaximusHD 10.0.0 - 4.2.2 Sense 5 -> will be the best one for ONE S
Will wait this with big impatience to be fixed and work of my favorite phone - One S
Thanks

i'm using this tutorials to try to debug liboemcamera.so:
http://forum.xda-developers.com/showthread.php?t=2050393
http://forum.xda-developers.com/showthread.php?t=1374345
but i'm currently stuck here:
http://forum.xda-developers.com/showpost.php?p=45827106&postcount=13
EDIT: solved few problem
but now, i'm stuck, again
ptrace: I/O error.

If someone want to try to debug native android library using IDA Pro...
[console 1] -> one time only
adb push the gdbserver from ndk to data/local/tmp
adb shell su
adb chmod 755 gdbserver
[console 2] -> don't forget it or debug client will not connect!
adb forward tcp:1111 tcp:1111
[console 3] -> start binary you want to debug (or binary that load library that you want to debug liboemcamera.so in my case, using mm-qcamera-app) -> leave it opened
adb shell
su
echo 0 > /proc/sys/kernel/randomize_va_space (this is to disable ASLR, that cause library to be loaded at random address)
cd system/bin
./mm-qcamera-app
1 or 2
[console 4]->leave it opened
adb shell
su
echo 0 > /proc/sys/kernel/randomize_va_space (just to be sure)
ps (look at PID of mm-qcamera-app)
cd data/local/tmp
./gdbserver --attach :1111 PID_NUMBER_of_mm-qcamera-app
[console 5]
(adb pull system/lib and system/bin here->C:/android-ndk-r9/toolchains/arm-linux-androideabi-4.6/prebuilt/windows-x86_64/bin)
(start gdb from ndk from command line)
gdb.exe
(gdb) set height 0
(gdb) set solib-search-path ./
(gdb) directory C:/android-ndk-r9/toolchains/arm-linux-androideabi-4.6/prebuilt/windows-x86_64/bin
(gdb) target remote 127.0.0.1:1111
Remote debugging using 127.0.0.1:1111
0x4005fe48 in ?? ()
(gdb) info sharedlibrary
Reading symbols from C:/android-ndk-r9/toolchains/arm-linux-androideabi-4.6/preb
uilt/windows-x86_64/bin/mm-qcamera-app...done.
WARNING: no debugging symbols found in C:/android-ndk-r9/toolchains/arm-linux-an
droideabi-4.6/prebuilt/windows-x86_64/bin/mm-qcamera-app.
Either the binary was compiled without debugging information
or the debugging information was removed (e.g., with strip or strip -g).
Debugger capabilities will be very limited.
For further information: http://wiki/Main/GdbFaq#No_debugging_symbols_found
From To Syms Read Shared Object Library
0x40003240 0x4000b978 No C:/android-ndk-r9/toolchains/arm-linux-andro
ideabi-4.6/prebuilt/windows-x86_64/bin/system/bin/linker
0x40055940 0x40085d0c No libc.so
0x400a07f4 0x400a0998 No libstdc++.so
0x400a4e80 0x400b5164 No libm.so
0x40044180 0x40045d44 No liblog.so
0x40027a18 0x4003059c No libcutils.so
0x4025f6a0 0x40263008 No libgemini.so
0x4022f578 0x402543cc No libmmjpeg.so
0x400ca8b0 0x40161250 No liboemcamera.so
0x40296638 0x40296b50 No libmmstillomx.so
0x402a1494 0x402a1630 No libimage-omx-common.so
0x4029a658 0x4029e414 No libimage-jpeg-enc-omx-comp.so
0x4028a284 0x40291a5c No libmmcamera_interface2.so
(gdb)
NOW you have information about library base address! Nice! Copy and paste these information
Now you can just use CTRL+C on console 4, and execute instruction for console 4 again, so we can debug using IDA this time
(IDA)
for new versions->Debugger, Debugger option, option, uncheck "Use hardware temporary breakpoints"
Debugger,Switch Debugger,Remote GDB debugger and check Set as default debugger
Debugger, Process option, applicazion path (../system/bin/blabla), input file (same or ../system/lib/libblabla.so if debugging lib), Hostname: localhost, Port 1111 (or select youself, you will need to use it for all commands) and check "Set as default network setting"
Now load the file you want to debug
File->Open->liboemcamera.so in my case->Ok/Load->Check "Manual load" from the popup->OK->Input 0:400ca8b0 in my case (base address)->Load all section or section that you need->Yes
Wait for autoanalysis, and do some static analysis by yourself, set some breakpoint, etc,etc
When you are ready to debug: Debugger,Start process, Yes
TADA! The ****ing IDA+gdb should now be able to do step by step debug, but i got a ****ing ptrace: I/O error.

using HTC One Mini libs + updating kernel camera parts from HTC One Mini source, front camera is working good, but rear camera quality is really really bad, need a fix
i'll post an alpha mod soon
zoom bug (green rectangle on jpeg) is still present
EDIT: quality became bad because of wrong Auto White Balance not working good with M4 libs, so with a clean installation it will still working good, but if you came from Zoe fix from Magio, you will need to go back to stock libs/camera apps or do a fresh installation
zoe is working but need camera.apk modding to force it (it should be easy, since apk can be decompiled almost to source code)

install over a stock camera
kernel with M4 kernel camera patch: http://www.4shared.com/zip/CRNRFvCD/fabane_ville_m4_cam_26_09_13_v.html
test M4 libs+camera: http://www.4shared.com/zip/wW302ToJ/FixedZoeMagioV4_M4_ville.html
front facing camera is working, zoe needs to be enabled camera.apk side

pirlano said:
install over a stock camera
kernel with M4 kernel camera patch: http://www.4shared.com/zip/CRNRFvCD/fabane_ville_m4_cam_26_09_13_v.html
test M4 libs+camera: http://www.4shared.com/zip/wW302ToJ/FixedZoeMagioV4_M4_ville.html
front facing camera is working, zoe needs to be enabled camera.apk side
Click to expand...
Click to collapse
Well this work over your old kernel to make the one xl roms boot
Sent from my HTC One S using Tapatalk 2

yes, camera part only is changed, tomorrow i'll work on camera.apk

pirlano said:
yes, camera part only is changed, tomorrow i'll work on camera.apk
Click to expand...
Click to collapse
Ok cool need any help send me a pm
Sent from my HTC One S using Tapatalk 2

Hey guys, I know this is still in development but when finished will it work with the Maximus Rom?
Sent from my HTC One S using xda app-developers app

razlack said:
Hey guys, I know this is still in development but when finished will it work with the Maximus Rom?
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
the question is not "when", but, "if"
i'll start lessons next week, so i will be unable to continue
EDIT:
today, instead of looking at m4 camera.apk, i tryed to fix ffc with stock kernel and m7 libs, i think i have found the solution, don't know if it will work, but it's the better idea that i have found until now
EDIT2:
mt9v113 seems to be incompatible with m7 libs, cannot found a solution, we need an experienced arm hacker or hex-rays arm decompiler (if someone use it at work, license is too expensive for home users)
an ather way it's to create a mt9v113_act.c driver, but i think i'm not able to do that, and if it will work, but maybe a dummy one will work too, will try when i have time
for now the only way it's to use m4 libs, so camera.apk needs hacking (this is much more easy), i will try tomorrow
I'm also trying to understand what's causing the zoom bug...
also with both m4 and m7 libs (with kernel patches to make camera working) manual touch autofocus seems to be buggy with slow motion mode and with 60fps mode
and camera auto white balance need a fix, i'm starting to think that it's better to mod our stock camera, without zoe...****ing close source libs...