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
Related
Bounty Link:
Use this to Donate to the Project Itself for all of those involved in the hardwork Jface,Doniqq, and myself
Bugs List (Last updated 9/5/11)
Code:
-FFC Squished on some versions
-FFC roatated 90 Degrees CW on V1.5 & Up
-FFC @ Full Res Video still shows green boxes (missing libs?)
Update (9/5/11): LG Cam V3.0 -Major Fixes in this one
Testing now... if all goes well expect update package shortly. 2:42AM EST
Stitch Shot: Confirmed working
Panorama Shot: Confirmed Working
Continuous Shot: Confirmed Working
Zoom while recording Video in all modes : Confirmed working
Touch to focus : Confirmed Working
Taking Pictures in portrait flipped : Confirmed working
Recording at 1080P @ 24 FPS / 720P @ 30 FPS : Confirmed Working
Download LG Cam V3.0: Here
Update (8/5/11): LGCam V1.5 - Fxied for Real This Time - for the trolls i mean the update package
Download LGCam V1.5: Here
THIS WILL NOT WORK ON CM7 OR ANYTHING BASED ON CM7/AOSP FOR NOW
Restore AOSP/OTA GB Cam
V1.4
Don't want to talk about it
Code:
V1.5 Updates:
-Fixed ZIP Package, now flashable, I promise (Damn Signtool replaced the com folder :/) :o
-Fixed 1080P @ 24FPS/30 FPS same as stock FROYO
-Fixed Zoom while recording Video
- Stock Cam Icon
- Still needs to fix FFC
-Enjoy, Report any bugs in the thread
-Donate and help me buy a bottle of Belevedere Black:)
V1.4
Burning in hell somewhere
Click to expand...
Click to collapse
flak0 said:
Hey Devs and ofcourse Doniqq first off amazing work on EB i love it. Im using the FR version. Ok so basically I am posting this thread because I figured out for sure why the LG Camera will not work on GB. It is not a lack of drivers like everyone has said. Basically when the Camera.Apk(LG Camera) is launched it looks for Libamce.so (i figured this out by reverse engineering the LG Camera and found the referrence on where it looks for the shared library libamce.so.) I went ahead and tried to push the LG Camera with the libamce.so yet still got a force close, this time the error was a reloc lbrary error looking for a _NZCamera6Connect function. I then went ahead an decompiled the libamce.so and found that it depends on libnvomx.so, then I decompiled libnvomx.so and found that it depends on libm.so, then I tried pushing all three libs to GB and still got a force close. After digging deep enough I found that libm.so depends on libcamera_client.so which I also decompiled and then I found the _NZCamera6Connect fuction is contained here. I attempted to push the libcamera_cleint.so to to GB and boot failed, then I tried editing the update-zip file to include the libcamera_client.so (From Froyo) and boot also failed. I am positive that once we get this libcamera_client.so ported from FROYO to GB the LG Camera will work. Luckily there is no dependency on the framework. This is where I need your help since I know your the dev who made EB possible or any Dev thats out there Faux, Morific Thanks.
Here is the header of the decompiled libamce.so just in case:
Click to expand...
Click to collapse
I'm no dev, but I just want to thank you for continuing to try and bring the LG cam to Gingerbread. Hopefully a dev will gladly help you out with this issue. Once again thank you for taking the time to try and get this hard headed app to work.
Sent from my LG-P999 using XDA Premium App
[depricated as of 9/5/11 - history of lgcam on gb]
Update (8/3/11): LG CAM for CM7 removed until fixed. Too many people were flashing on MIUI and CM7 Based ROMS
New Version for Stock OTA based ROMS coming out tonight.
Proposed fixes include -> 24/30 FPS @ 1080P and Zoom while video recording
Also moved some of the original OP two posts down to clean up the OP.
Update(8/2/11): LG Cam for CM 7 Beta
Below is what you have all been asking for, it is a beta of LG Cam for CM7. If you are willing to take the risk go ahead and flash BUT FIRST MAKE SURE YOU NANDROID. I have also attached CM7 Cam again if it fails to work and/or if you wish to go back. Please update the thread with any errors, logcats preferred.
Edit: Update(8/2/11 @ 4:42AM EST) below.
I was able to Port the LGE folder from GB to CM7 into the framework successfully however now when I open the CAM I am getting a null pointer exception. Anyone willing to help here please.
Code:
I/ActivityManager( 1074): Starting: Intent { act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10200000 cmp=com.android.camera/.ArcCamera } from pid 1279
I/ActivityManager( 1074): Start proc com.android.camera for activity com.android.camera/.ArcCamera: pid=3750 uid=10034 gids={1006, 1015}
D/ ( 984): NVRM_DAEMON(819): rt_exist=2, add client ref
D/ ( 984): set continue (1280x960)
D/ ( 984): set continue (1280x1024)
D/ ( 984): set continue (1280x1024)
D/ ( 984): set continue (1360x768)
D/ ( 984): set continue (1440x900)
D/ ( 984): set continue (1680x1050)
D/ ( 984): set BetterMode (1280x720)
D/ ( 984): set BetterMode (1920x1080)
D/ ( 984): set BetterMode (1280x720)
D/ ( 984): set BetterMode (1920x1080)
D/ ( 984): set BetterMode (1920x1080)
D/ ( 984): set BetterMode (1920x1080)
D/ ( 984): set BetterMode (1920x1080)
I/WindowManager( 1074): Setting rotation to 1, animFlags=1
I/ActivityManager( 1074): Config changed: { scale=1.0 imsi=310/260 loc=en_US touch=3 keys=1/1/2 nav=1/1 orien=2 layout=34 uiMode=17 seq=7 themeResource=null}
I/PowerWidget( 1243): Clearing any old widget stuffs
I/PowerWidget( 1243): Setting up widget
I/PowerWidget( 1243): Default buttons being loaded
I/PowerWidget( 1243): Button list: toggleWifi|toggleBluetooth|toggleGPS|toggleSound
I/PowerWidget( 1243): Setting up button: toggleWifi
I/PowerWidget( 1243): Setting up button: toggleBluetooth
I/PowerWidget( 1243): Setting up button: toggleGPS
I/PowerWidget( 1243): Setting up button: toggleSound
D/szipinf ( 3750): Initializing inflate state
I/===ArcCamera=== 1.1.0.1( 3750): Performance log:Load so2011-08-02 08:36:10.376 cost:6ms
I/===ArcCamera=== 1.1.0.1( 3750): Performance log:Launch camera
[color="blue"][size="4"]major update 7/28/11[/size]
[/color]
working lg cam on 2.3.3 ota & xborders stock rom (huge thanks to jumaaneface) once the cam is confirmed working on cm7 & aosp the bounty will be paid. I will also be looking into the actual cam app by decompiling source to see if we can fix the 1080p recording to make it record at 30 fps.
Again thanks to all the supporters and to jumaaneface who made this possible.
:d hey devs and ofcourse doniqq first off amazing work on eb i love it. Im using the fr version. Ok so basically i am posting this thread because i figured out for sure why the lg camera will not work on gb. It is not a lack of drivers like everyone has said. Basically when the camera.apk(lg camera) is launched it looks for libamce.so (i figured this out by reverse engineering the lg camera and found the referrence on where it looks for the shared library libamce.so.) i went ahead and tried to push the lg camera with the libamce.so yet still got a force close, this time the error was a reloc lbrary error looking for a [b]_nzcamera6connect[/b] function. I then went ahead an decompiled the libamce.so and found that it depends on libnvomx.so, then i decompiled libnvomx.so and found that it depends on libm.so, then i tried pushing all three libs to gb and still got a force close. After digging deep enough i found that libm.so depends on libcamera_client.so which i also decompiled and then i found the [b]_nzcamera6connect[/b] fuction is contained here. I attempted to push the libcamera_cleint.so to to gb and boot failed, then i tried editing the update-zip file to include the libcamera_client.so (from froyo) and boot also failed. I am positive that once we get this libcamera_client.so ported from froyo to gb the lg camera will work. Luckily there is no dependency on the framework. This is where i need your help since i know your the dev who made eb possible or any dev thats out there faux, morific thanks.
[b]update(7/27/11): Bounty increased to $100.00 thanks to:
[quote]eleeo037037 :$10
adevilfish :$10
bakedpatato : $5.00[/quote][/b]
[b]major update (7/26/11)
since the ota is official and the lg cam is not contained i am starting a bounty at $75.00 for the first person who can figure this out. I have tried numerous attempts using different approaches to no avail. There are others in the thread who mentioned they will also put up a bounty. I alone will pay $75.00 plus whatever anyone else decides to throw in the pot. [/b]
[b]update 3 (7/22/11): Attempted again to change some files in the framework and upon boot logcat threw error for missing decl from the camera$files in the framework. I pushed the libcamera_client.so from froyo and then the messaged changed to this:
[quote]i//system/xbin/busybox( 1015): Sysctl: /etc/sysctl.conf: No such file or directory
i//system/xbin/busybox( 1015): -k: No such file or directory
i//system/xbin/busybox( 1015): [: 61m: Bad number[/b][/quote]
[b]update 2(7/22/11) : Flashing eb 1.0.5 gr v21e rom with modified framework and it failed, so i pushed libcamera_client.so and it failed, error below [/b]
[quote]- waiting for device -
--------- beginning of /dev/log/main
i/netd ( 1018): Netd 1.0 starting
--------- beginning of /dev/log/system
i/vold ( 1017): Vold 2.1 (the revenge) firing up
d/vold ( 1017): Usb_configuration switch is not enabled in the kernel
d/vold ( 1017): Volume extsdcard state changing -1 (initializing) -> 0 (no-media)
d/vold ( 1017): Volume sdcard state changing -1 (initializing) -> 0 (no-media)
d/vold ( 1017): Volume extsdcard state changing 0 (no-media) -> 1 (idle-unmounted)
w/vold ( 1017): Duplicate state (1)
d/vold ( 1017): Volume sdcard state changing 0 (no-media) -> 1 (idle-unmounted)
w/vold ( 1017): Duplicate state (1)
w/vold ( 1017): Duplicate state (1)
i/debug ( 1019): Debuggerd: Jul 15 2011 10:15:43
d/ ( 1029): Open is ok, now, we are in user_land!
D/ ( 1029): Set continue (1280x960)
d/ ( 1029): Set continue (1280x1024)
d/ ( 1029): Set continue (1280x1024)
d/ ( 1029): Set continue (1360x768)
d/ ( 1029): Set continue (1440x900)
d/ ( 1029): Set continue (1680x1050)
d/ ( 1029): Set bettermode (1280x720)
d/ ( 1029): Set bettermode (1920x1080)
d/ ( 1029): Set bettermode (1280x720)
d/ ( 1029): Set bettermode (1920x1080)
d/ ( 1029): Set bettermode (1920x1080)
d/ ( 1029): Set bettermode (1920x1080)
d/ ( 1029): Set bettermode (1920x1080)
d/kipc ( 1020): Kipc_init()
d/kipc ( 1020): Address is 127.0.0.1, port is 45211
d/kipc ( 1020): Binding...
D/kipc ( 1020): Listening...
D/kipc ( 1020): Accepting...
D/ganril ( 1020): Gan ril starting
d/ganril ( 1020): Entering main loop
d/ganat ( 1020): 65 6e 74 65 72 69 6e 67 20 6d 61 69 6e 4c 6f 6f
d/ganat ( 1020): 70 28 29
d/ganat ( 1020): Gan_at_open
d/ganpsat ( 1020): Gan_ps_at_open
d/ganat ( 1020): Additional logging enabled. Going to call readline()
d/ganat ( 1020): Readline
d/ganat ( 1020): Readline : Before read
i/ ( 1030): Screencaptured accept lsocket: 9
i/vold ( 1017): Usb_mass_storage function disabled
e/netlinkevent( 1017): Netlinkevent::findparam(): Parameter 'switch_name' not found
e/netlinkevent( 1017): Netlinkevent::findparam(): Parameter 'switch_state' not found
w/vold ( 1017): Switch /devices/virtual/switch/usb_mass_storage event missing name/state info
i/rescuestarter( 1026): Rescuestarter 6.3.274 starts
i/rescuestarter( 1026): Ready, waiting for connection
e/netlinkevent( 1017): Netlinkevent::findparam(): Parameter 'switch_name' not found
e/netlinkevent( 1017): Netlinkevent::findparam(): Parameter 'switch_state' not found
w/vold ( 1017): Switch /devices/virtual/switch/usb_mass_storage event missing name/state info
i//system/xbin/busybox( 1015): Sysctl: /etc/sysctl.conf: No such file or directory
i//system/xbin/busybox( 1015): -k: No such file or directory
i//system/xbin/busybox( 1015): [: 61m: Bad number
i/vold ( 1017): Usb_mass_storage function enabled
d/vold ( 1017): Share method ums now available
i//system/xbin/busybox( 1015): Mount: Invalid argument
i//system/xbin/busybox( 1015): Run-parts: /system/etc/init.d/10ext4tuneup exited with code 255
i//system/xbin/busybox( 1015): Starting automatic zipalign 07-22-2011 22:21:12
i//system/xbin/busybox( 1015): Zipalign: Not found
i//system/xbin/busybox( 1015): Zipalign already completed on /data/app/*.apk
i//system/xbin/busybox( 1015): Zipalign: Not found
i//system/xbin/busybox( 1015): Zipalign already completed on /system/app/accountandsyncsettings.apk
i//system/xbin/busybox( 1015): Zipalign: Not found
i//system/xbin/busybox( 1015): Zipalign already completed on /system/app/applicationsprovider.apk
i//system/xbin/busybox( 1015): Zipalign: Not found
i//system/xbin/busybox( 1015): Zipalign already completed on /system/app/bluetoothopp.apk
i//system/xbin/busybox( 1015): Zipalign: Not found
i//system/xbin/busybox( 1015): Zipalign already completed on /system/app/bluetoothpbap.apk
i//system/xbin/busybox( 1015): Zipalign: Not found[/quote]
[b]update 7/22/11 - working on patching and porting elements from the froyo framework to gb[/b]
[img]http://forum.xda-developers.com/attachment.php?attachmentid=662618&stc=1&d=1311355083[/img]
[b](7/21/11)major update: Lg releases stock gb rom v21e however lg cam is not on board. This thread will.continue until we can successfully port the lg cam to gb. [/b]
[b]update 7/20/2011:
[quote]status update: Spoke with doniqq via pm he is working hard for us (so please thank him) to port the lg cam from froyo to gb. I am going to take another stab at this tonight and check 1 more thing. For those that had/have the nexus 1, i was the one who successfully ported the cm camera to rodriguez miui when everyone thought it was impossible. I am pretty sure the framework.jar is not part of this however when i moved the cm 7 cam to miui i did modify the framework, so i will take a look at this tonight before ruling it out completely.
[/quote][/b]
[b]here is the header of the decompiled libamce.so just in case:[/b]
[quote].plt:000459f4 ;
.plt:000459f4 ; +-------------------------------------------------------------------------+
.plt:000459f4 ; | this file has been generated by the interactive disassembler (ida) |
.plt:000459f4 ; | copyright (c) 2009 by hex-rays, |
.plt:000459f4 ; | license info: B3-ada1-9d85-df |
.plt:000459f4 ; | licensed user |
.plt:000459f4 ; +-------------------------------------------------------------------------+
.plt:000459f4 ;
.plt:000459f4 ; input md5 : 2ebb5ff4c8e8cf34c40ffc3aed9e8042
.plt:000459f4
.plt:000459f4 ; ---------------------------------------------------------------------------
.plt:000459f4 ; file name : C:\users\flak0-hpn3\downloads\libamce.so
.plt:000459f4 ; format : Elf (shared object)
.plt:000459f4 ; imagebase : 8000
.plt:000459f4 ; needed library 'libcamera_client.so'
.plt:000459f4 ; needed library 'libsurfaceflinger_client.so'
.plt:000459f4 ; needed library 'libui.so'
.plt:000459f4 ; needed library 'liblog.so'
.plt:000459f4 ; needed library 'libcutils.so'
.plt:000459f4 ; needed library 'libutils.so'
.plt:000459f4 ; needed library 'libhardware.so'
.plt:000459f4 ; needed library 'libmedia.so'
.plt:000459f4 ; needed library 'libandroid_runtime.so'
.plt:000459f4 ; needed library 'libc.so'
.plt:000459f4 ; needed library 'libm.so'
.plt:000459f4 ; needed library 'libstdc++.so'
.plt:000459f4 ; needed library 'libdl.so'
.plt:000459f4 ; needed library 'libbinder.so'
.plt:000459f4 ; needed library 'libskia.so'
.plt:000459f4 ; needed library 'libicuuc.so'
.plt:000459f4 ; needed library 'libegl.so'
.plt:000459f4 ; needed library 'libnvomx.so'
.plt:000459f4 ;
.plt:000459f4 ; eabi version: 5
.plt:000459f4 ;
.plt:000459f4
[/quote][/quote]
Click to expand...
Click to collapse
anybody try contacting faux or morfic to see if they could take a look? They are both very cool guys. I can talk to them if you want.
I have a silly question? If you use titanium back up and restore the LG camera would that work? If not, why?
I contacted both of them plus numerous devs.
jdkackley said:
anybody try contacting faux or morfic to see if they could take a look? They are both very cool guys. I can talk to them if you want.
Click to expand...
Click to collapse
Sent from my LG-P999 using XDA App
ClausMontoya said:
I have a silly question? If you use titanium back up and restore the LG camera would that work? If not, why?
Click to expand...
Click to collapse
I know it wont work but I couldnt tell you why. I thought the same thing and have tried it.
bls2633 said:
I know it wont work but I couldnt tell you why. I thought the same thing and have tried it.
Click to expand...
Click to collapse
Doesn't Titanimum just back up the apk file and not the compiled shared object?
Even so it'd be scary to think that it would somehow overwrite shared objects, potentially breaking the OS.
ClausMontoya said:
I have a silly question? If you use titanium back up and restore the LG camera would that work? If not, why?
Click to expand...
Click to collapse
I believe that what has been explained above is that there are libraries that the apk depend on to function that are not available on CM7 at the moment. (I could be wrong though)
yeah it's a similar reason if you backup DSP Manager from CM7 and try to install it on stock it will basically do nothing.
hey everyone i am still waiting for some devs to respond. Doniqq said he would take a look and let me know. We are 90% to having the LG Cam on GB.
If anyone else is good with shared objects in Android let me know.
Can you post the libcamera_client.so decompiled?
In theory this should be fairly simple to compile under gingerbread.
Scyth3 said:
Can you post the libcamera_client.so decompiled?
In theory this should be fairly simple to compile under gingerbread.
Click to expand...
Click to collapse
I can post it but i don't think it will compile, Remember i used a deconplier to reveal the source.
Sent from my LG-P999 using XDA App
I'll join in on this when I get home later. Has anyone tried contacting LG? They seem pretty reasonable.
Nah he means like talking to them about the camera drivers and what not I'm sure he wont say he'd trying to convert there froyo camera app to work with gingerbread lol they should be pretty reasonable
Yeah that's what I meant. I figure if there's something we need they might be able to help us. OP PM me
Status Update: 7/20/2011 US EST
Status Update: Spoke with Doniqq via PM he is working hard for us (so please thank him) to port the LG Cam from Froyo to GB. I am going to take another stab at this tonight and check 1 more thing. For those that had/have the Nexus 1, I was the one who successfully ported the CM Camera to Rodriguez MIUI when everyone thought it was impossible. I am pretty sure the framework.jar is not part of this however when I moved the CM 7 cam to MIUI I did modify the framework, so I will take a look at this tonight before ruling it out completely.
Thank u everyone, your thank yous motivate that much more. I will keep u updated.
Sent from my LG-P999 using XDA App
Its solved because i believe the reason why the LG cam won't work has been found and the culprit is the libcamera_client.so from Froyo to GingerBread. Its now requires the work of a dev to port. Just saying
Sent from my LG-P999 using XDA App
Thanks to Chuckhriczko who is also jumping on board to help.
Faux responded and respectfully informed me that he is working on several projects however if he has some spare time he will take a look for us.
Sent from my LG-P999 using XDA App
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.
This one is fun - I'm getting an FC every time an application requests keyboard input. If I hit the Google search icon on the top left of the home screen, it immediately FCs - that's what I'm using to test.
I downloaded aLogCat to the device via Google Play on my desktop, and ran it. Here is what I believe to be the relevant log section , from tapping the search icon, to re-entering aLogCat.
I believe the ClipboardEx service is causing the issue, possibly as an interference with another app I have installed - but I don't know what, or how to give you guys a list of apps installed without just typing each one.
This issue happened once to me, and a factory restore fixed it - two weeks later, and it's back. I'm not an experience Android guy, though I am a nerd and a developer. Surely this is something fixable. Does anyone have any thoughts on what could be causing this?
Code:
I/InputReader( 184): Touch event's action is 0x1 (deviceType=0) [pCnt=1, pending(waiting finished signal)=1, s=]
I/InputDispatcher( 184): Delivering touch to current input target: action: 0x1
I/InputDispatcher( 184): Delivering touch to current input target: action: 0x1
I/InputDispatcher( 184): Delivering touch to current input target: action: 0x1
I/ActivityManager( 184): START {intent.toShortString} from pid 383
D/PowerManagerService( 184): acquireDVFSLockLocked : type : DVFS_MIN_LIMIT frequency : 1008000 uid : 1000 pid : 184 tag : ActivityManager
W/ActivityManager( 184): mDVFSLock.acquire()
D/Launcher.HomeFragment( 383): onPause
D/Launcher( 383): onPause
V/TaskCloserActivity( 3234): TaskCloserActivity onReceive()
D/KeyguardViewMediator( 184): setHidden false
D/ActivityManager( 184): Trying to launch applicationName
D/ControlPanelRemoteService( 3246): onDestroy()
D/OpenGLRenderer( 383): Flushing caches (mode 1)
D/dalvikvm( 3157): GC_CONCURRENT freed 259K, 5% free 6784K/7111K, paused 2ms+3ms
D/KeyguardViewMediator( 184): setHidden false
D/STATUSBAR-StatusBarManagerService( 184): setSystemUiVisibility(0x0)
D/STATUSBAR-StatusBarManagerService( 184): manageDisableList what=0x0 pkg=WindowManager.LayoutParams
D/libEGL ( 3157): loaded /vendor/lib/egl/libEGL_POWERVR_SGX540_120.so
D/libEGL ( 3157): loaded /vendor/lib/egl/libGLESv1_CM_POWERVR_SGX540_120.so
D/libEGL ( 3157): loaded /vendor/lib/egl/libGLESv2_POWERVR_SGX540_120.so
D/OpenGLRenderer( 3157): Enabling debug mode 0
E/ClipboardServiceEx( 3157): Had failed to obtaining clipboardEx service.
D/AndroidRuntime( 3157): Shutting down VM
W/dalvikvm( 3157): threadid=1: thread exiting with uncaught exception (group=0x40bb01f8)
E/AndroidRuntime( 3157): FATAL EXCEPTION: main
E/AndroidRuntime( 3157): java.lang.NullPointerException
E/AndroidRuntime( 3157): at android.sec.clipboard.ClipboardExManager.updateData(ClipboardExManager.java:241)
E/AndroidRuntime( 3157): at android.widget.EditText.onFocusChanged(EditText.java:134)
E/AndroidRuntime( 3157): at android.view.View.handleFocusGainInternal(View.java:3727)
E/AndroidRuntime( 3157): at android.view.View.requestFocus(View.java:5420)
E/AndroidRuntime( 3157): at android.view.ViewGroup.onRequestFocusInDescendants(ViewGroup.java:2154)
E/AndroidRuntime( 3157): at android.view.ViewGroup.requestFocus(ViewGroup.java:2110)
E/AndroidRuntime( 3157): at android.view.ViewGroup.onRequestFocusInDescendants(ViewGroup.java:2154)
E/AndroidRuntime( 3157): at android.view.ViewGroup.requestFocus(ViewGroup.java:2110)
E/AndroidRuntime( 3157): at android.view.ViewGroup.onRequestFocusInDescendants(ViewGroup.java:2154)
E/AndroidRuntime( 3157): at android.view.ViewGroup.requestFocus(ViewGroup.java:2110)
E/AndroidRuntime( 3157): at android.view.ViewGroup.onRequestFocusInDescendants(ViewGroup.java:2154)
E/AndroidRuntime( 3157): at android.view.ViewGroup.requestFocus(ViewGroup.java:2110)
E/AndroidRuntime( 3157): at android.view.ViewGroup.onRequestFocusInDescendants(ViewGroup.java:2154)
E/AndroidRuntime( 3157): at android.view.ViewGroup.requestFocus(ViewGroup.java:2110)
E/AndroidRuntime( 3157): at android.view.ViewGroup.onRequestFocusInDescendants(ViewGroup.java:2154)
E/AndroidRuntime( 3157): at android.view.ViewGroup.requestFocus(ViewGroup.java:2113)
E/AndroidRuntime( 3157): at android.view.View.requestFocus(View.java:5370)
E/AndroidRuntime( 3157): at android.view.ViewRootImpl.performTraversals(ViewRootImpl.java:1598)
E/AndroidRuntime( 3157): at android.view.ViewRootImpl.handleMessage(ViewRootImpl.java:2459)
E/AndroidRuntime( 3157): at android.os.Handler.dispatchMessage(Handler.java:99)
E/AndroidRuntime( 3157): at android.os.Looper.loop(Looper.java:137)
E/AndroidRuntime( 3157): at android.app.ActivityThread.main(ActivityThread.java:4514)
E/AndroidRuntime( 3157): at java.lang.reflect.Method.invokeNative(Native Method)
E/AndroidRuntime( 3157): at java.lang.reflect.Method.invoke(Method.java:511)
E/AndroidRuntime( 3157): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:790)
E/AndroidRuntime( 3157): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:557)
E/AndroidRuntime( 3157): at dalvik.system.NativeStart.main(Native Method)
W/ActivityManager( 184): Force finishing activity com.google.android.googlequicksearchbox/.SearchActivity
E/android.os.Debug( 184): [email protected] > dumpstate -k -t -n -z -d -o /data/log/dumpstate_app_error
I/dumpstate( 3272): begin
W/ActivityManager( 184): Activity pause timeout for ActivityRecord{423f3fe0 com.google.android.googlequicksearchbox/.SearchActivity}
W/PowerManagerService( 184): Timer 0x7->0x3|0x0
I/PowerManagerService( 184): Ulight 7->3|0
D/PowerManagerService( 184): setLightBrightness : mButtonLight : 0
E/lights ( 184): write_int failed to open /sys/class/sec/sec_touchkey/brightness
I/InputReader( 184): Touch event's action is 0x0 (deviceType=0) [pCnt=1, pending(waiting finished signal)=0, s=0.70 ]
E/lights ( 184): write_int failed to open /sys/class/sec/sec_touchkey/brightness
I/PowerManagerService( 184): Ulight 3->7|0
D/PowerManagerService( 184): setLightBrightness : mButtonLight : 140
I/InputReader( 184): Touch event's action is 0x1 (deviceType=0) [pCnt=1, pending(waiting finished signal)=0, s=]
D/VoldCmdListener( 89): asec list
D/VoldCmdListener( 89): CommandListener::AsecCmd::runCommand -> --
I/dumpstate( 3272): done
D/KeyguardViewMediator( 184): setHidden false
D/Launcher( 383): onResume
D/STATUSBAR-StatusBarManagerService( 184): setSystemUiVisibility(0x0)
D/STATUSBAR-StatusBarManagerService( 184): manageDisableList what=0x0 pkg=WindowManager.LayoutParams
D/myTest ( 383): [MonthTheme] onResume!!
D/KeyguardViewMediator( 184): setHidden false
D/myTest ( 383): firstDayOfWeek = -1
I/power ( 184): *** release_dvfs_lock : lockType : 1
D/myTest ( 383): [MonthView] updateView.mStartDay: 1
D/DEFERED_APP_VISIBILITY( 184): tweaking closing app
D/PowerManagerService( 184): releaseDVFSLockLocked : all DVFS_MIN_LIMIT are released
W/ActivityManager( 184): mDVFSLock.release()
D/Launcher.HomeFragment( 383): onResume
I've now removed all downloaded applications from my Tab. No dice.
I'm going to see if I can dig up any more logs, then reset it I guess.
I've discovered that copying something to the clipboard also causes the FC. This is definitely an issue with TouchWiz's clipboard as far as I can figure out.
Weird because I know I've copy pasted from the tab before
Sent from my SAMSUNG-SGH-I727 using xda premium
jamesd86 said:
Weird because I know I've copy pasted from the tab before
Sent from my SAMSUNG-SGH-I727 using xda premium
Click to expand...
Click to collapse
It works for me, too, until the whole thing starts crashing, lol.
I reset to factory and re-installed all my stuff; it seems to be working now. I guess it's Samsung's way of reminding me to keep regular backups...
My tab crashed and then this same exact thing started happening. The logs mentioned ClipboardServiceEx.
I am rooted, so I started an adb shell and found that /data/clipboard has all the persistent clipboard entries (I love that feature by the way).
I did this:
su
mv /data/clipboard /data/oldclipboard
mkdir /data/clipboard
chmod 775 /data/clipboard
chown system.system /data/clipboard
reboot
This fixed it, although it cleared all my "held" info in the clipboard. A small price to pay. If you really had to, you could probably fish in /data/oldclipboard for it. Of course, now I will go delete oldclipboard.
Hope that helps someone.
Thanks for that info, you never know!
Pp.
Transmitted from another galaxy with an Infected P-5113.
same thing happening to me. but i was prompted to update my device so i clicked yes thinking it would fix the problem now im stuck on the "use google location" page of the setup forms because when i click next i guess theres a keyboard involved so it crashes. only other button is a back arrow which does nothing.
i havent ever messed with this stuff but i guess ill have to find out how to factory reset through the usb cable.
unwanted pain in the butt
dorkmo said:
same thing happening to me. but i was prompted to update my device so i clicked yes thinking it would fix the problem now im stuck on the "use google location" page of the setup forms because when i click next i guess theres a keyboard involved so it crashes. only other button is a back arrow which does nothing.
i havent ever messed with this stuff but i guess ill have to find out how to factory reset through the usb cable.
unwanted pain in the butt
Click to expand...
Click to collapse
If you plan to root, just do that, boot into recovery, do an adb shell and clear the clipboard directory.
If you aren't going to install a custom recovery then yeah, wipe it out.
wd5gnr said:
If you plan to root, just do that, boot into recovery, do an adb shell and clear the clipboard directory.
If you aren't going to install a custom recovery then yeah, wipe it out.
Click to expand...
Click to collapse
ok newbie here with samsung tabs having same problem, how do you boot into recovery and do an adb shell ? can see above how to clear the clipboard directory and i dont want to factory reset too hard to reload all the crap on ....
thanks
I had the same problem, I do not want to root my device, but I like to use the standard key board from Sumsung. I send a a-mail to a lot of dutch companies (resellers) to tell them about the problem. I think that Sansung must make a firware update to solve this problem. I what to ask all people who have problems with the keyboard to e-mail Samsung and there reseller to put preasure on Samsung to make a firmware.
I use a work a round, I use a 3e party keyboard untill Samsung makes a firmware update.
wd5gnr said:
I did this:
su
mv /data/clipboard /data/oldclipboard
mkdir /data/clipboard
chmod 775 /data/clipboard
chown system.system /data/clipboard
reboot
Hope that helps someone.
Click to expand...
Click to collapse
YEZZZZZ THANK YOU VERY MUCH!!!:good::laugh:
This worked perfectly on my Samsung Galaxy Tab 2 10.1 (P5110)
Thanks wd5gnr for the solution, worked very well!
Regards.
Glad it helped. I noticed someone asked earlier for more details.
There are plenty of root tutorials here. As for installing ADB there are a few ways to go and it depends on your PC's OS and if you want to get someone's simplified package or not. Read: http://www.howtogeek.com/125769/how-to-install-and-use-abd-the-android-debug-bridge-utility/ and the comments on that page too. If you google something like "installing ADB" you should find lots of help.
Once you have adb installed and can get to a shell, you should be good with my earlier instructions.
Any developer here??? Pls help me to fix bt media... My rom is HTC Sense 4 for htc explorer/pico which is ported by derefas from HTC Desire C. Bluetooth file transfer works very well but bt headset doesnt work. Here is the logcat.
E/BluetoothA2dpService.cpp( 349): onConnectSinkResult: D-Bus error: org.bluez.E
rror.Failed (Stream connection failed)
D/BluetoothA2dpService( 349): checkSinkSuspendState(): state=0,mTargetA2dpState
=-1
D/StateMachine( 349): handleMessage: new destination call exit
D/StateMachine( 349): invokeExitMethods: PendingCommandState
I/BluetoothProfileState( 349): Message:Entering Stable State
D/AudioService( 349): isSpecialCase=true , mEventAudioOnly=false , isStreamActi
ve=false
D/AudioService( 349): checkEqIdAndApplyEffect isHeadsetPlugged()=false , mBluet
oothHeadsetConnected=false , id=900 , mHtcSpecificAP=false , mGlobalSoundEffect=
900
V/AudioHardwareMSM72XX( 114): setParameters() global_effect=none
D/AudioService( 349): broadcastSoundEffectChanged beats state=false appName=BT
state changed
V/BluetoothEventManager( 2780): Received android.bluetooth.a2dp.profile.action.C
ONNECTION_STATE_CHANGED
I/LocalBluetoothProfileManager( 2780): Failed to connect A2DP device
D/StateMachine( 349): handleMessage: new destination call exit
D/StateMachine( 349): invokeExitMethods: OutgoingA2dp
I/BluetoothDeviceProfileState( 349): Entering ACL Connected state with: 102
D/BluetoothA2dpService( 349): A2DP state : device: C4:85:08:05:59:5A State:1->0
I/BluetoothA2dpService( 349): [embedded] A2DP state : address: C4:85:08:05:59:5
A name: SHEKHAR-PC State:1->0
D/BluetoothAdapterStateMachine( 349): BluetoothOn process message: 52
D/BluetoothService( 349): CONNECTION_STATE_CHANGE: C4:85:08:05:59:5A: 1 -> 0
V/BluetoothEventManager( 3562): Received android.bluetooth.a2dp.profile.action.C
ONNECTION_STATE_CHANGED
I/LocalBluetoothProfileManager( 3562): Failed to connect A2DP device
I/USERIAL_LINUX( 3593): ##### USERIAL_Ioctl: BT_Sleep, USERIAL_IO_BT_WAKE_DEASSE
RT ####
D/PhoneStatusBarPolicy( 634): isCdma():false hasService:true mSimState=UNKNOWN
gprsState=0 mDataState=0 dataActivity=1 mPhone.htcModemLinkOn:false hspa==true
E/ ( 3593): btm_sec_disconnected - Clearing Pending flag
W/ ( 3593): BTA_DM_LINK_DOWN_EVT::bdaddr c4:85:08:05:59:5a reason x13
I/ ( 3593): send_ctrl_msg: [BTL_IFS CTRL] send BTLIF_DTUN_SIGNAL_EVT (CTR
L) 11 pbytes (hdl 22)
D/DTUN_HCID4( 3608): dtun_dm_sig_link_down()
I/DTUN_HCID4( 3608): dtun_dm_sig_link_down device = 0x6f7900 reason = 19
I/DTUN_HCID4( 3608): [embedded]LINK_DOWN name = SHEKHAR-PC, address = C4:85:08:0
5:59:5A, reason = 0x13
D/BluetoothEventLoop( 349): Device property changed: C4:85:08:05:59:5A property
: Connected value: false
D/ ( 3593): >>> STOP GKI_timer_update(), wake_lock_count:0
D/ ( 3593): >>> SUSPENDED GKI_timer_update()
Can anyone guide me to fix this?
Camera works few days when i do a clean install of original rom. Or sometimes witrh custom rom. But after few days or hours camera starts closing. With original rom/ruu it doesn't say anything but custom rom says "can't connect to camera" and camera closes. Factory reset with original rom works sometimes but not allways. I have tried wiping cahce etc, fix permissions, other camera apps, clean install, w/ and w/o sd-card. Allways the same. Camera stops working.
Here is logcat:
http://pastebin.com/KrAT91wm
I made new logcat. Trying to make it shorter. http://pastebin.com/HkFwwMu0 This is with Viper ROM.
Is this the problem? How to solve it?
PHP:
W/mm-camera( 160): whichCamera no 2nd camera
I/mm-camera( 160): set sensor selection :0
D/mm-camera( 160): mm_camera_init, open FD: -1
E/mm-camera( 160): mm_camera_init: controlFd is invalid No such file or directory FD: -1
E/QualcommCameraHardwareZSL( 160): startCamera: mm_camera_init failed:
E/QualcommCameraHardwareZSL( 160): createInstance: startCamera failed!
E/CameraService( 160): Could not open camera 0: -1
I/CameraService( 160): Destroying camera 0