Whenever I open the camera app it force closes. Also when I wipe cache and data the the camera app opens and when I try to switch to the front facing camera it crashes. Any ideas? I'm using the stock jelly bean ROM.
Sent from my Nexus S using xda app-developers app
acseazzu said:
Whenever I open the camera app it force closes. Also when I wipe cache and data the the camera app opens and when I try to switch to the front facing camera it crashes. Any ideas? I'm using the stock jelly bean ROM.
Sent from my Nexus S using xda app-developers app
Click to expand...
Click to collapse
If the app is a origianl JB app maybe your ROM Is corrupted try to reflash ROM
If this camera app is a play store app redownload it or try another one.
S.R.
i had so such problem, to be on the safe side, just redownload and reinstall the rom, or try a custom rom
I have same problem... I tried reloading stock JB but always same force close problem, and with custom JB rpm it always show block when switching to front camera. I am afraid if front camera hardware is broken or what???
Its the gallery apk. I have tried other jb ROMs and they all crash it. Any other ideas?
Sent from my Nexus S using xda app-developers app
Having the same issue as the OP..
Any solution to fix it?
acseazzu said:
Whenever I open the camera app it force closes. Also when I wipe cache and data the the camera app opens and when I try to switch to the front facing camera it crashes. Any ideas? I'm using the stock jelly bean ROM.
Sent from my Nexus S using xda app-developers app
Click to expand...
Click to collapse
Has the front camera always been this way?
Or just with JB?
Have u always been stock?
At what point did u notice the issue?
The more info the better.... thx
Vs Nexus S4G using tapatalk2
I have exactly same problem too.
It started after update to JB. No software can work with front facing camera (not standart, not cameras from market, not Skype, not Google+).
And now it doesn't work even if I flash stock images from Google.
I tried:
1. Stock JRO03L, JRO03E, IMM76D (with radio and recovery) (from developers[dot]google[dot]com)
2. CNA 3.6.6.
3. CM10 Nightly
4. AOKP JB 4
always tried with full wipe and formating sdcard. Now I have CNA 3.6.6., but camera always crashes, when I switch it to front-face.
Where can I find any interesting Crash logs, from which I can find out source of a problem?
Also after update I had problems with gallery (it was empty, until I cleared EXIF from my 5 Camera360 images), maybe this is correlated somehow...
svekl said:
I have exactly same problem too.
It started after update to JB. No software can work with front facing camera (not standart, not cameras from market, not Skype, not Google+).
And now it doesn't work even if I flash stock images from Google.
I tried:
1. Stock JRO03L, JRO03E, IMM76D (with radio and recovery) (from developers[dot]google[dot]com)
2. CNA 3.6.6.
3. CM10 Nightly
4. AOKP JB 4
always tried with full wipe and formating sdcard. Now I have CNA 3.6.6., but camera always crashes, when I switch it to front-face.
Where can I find any interesting Crash logs, from which I can find out source of a problem?
Also after update I had problems with gallery (it was empty, until I cleared EXIF from my 5 Camera360 images), maybe this is correlated somehow...
Click to expand...
Click to collapse
Quick question:
After u formated ur SD card, what files do put back on it?
Whatever recovery u have, Try just putting back UR recovery folded but with only ur backup files when that ff camera worked... ICS and GB.
Then also put zips of a newer JB ROM and its gapps.
So boot into recovery and restore to one of ur backups where ff camera worked. Then see if it works.
If it doesn't, then hopefully u have insurance... if so unroot and turn it in.
But
If the camera does work then u r back in business. Just flash a newer JB ROM and see what happens.
Good luck
Vs Nexus S4G using tapatalk2
vidaljs said:
Quick question:
After u formated ur SD card, what files do put back on it?
Click to expand...
Click to collapse
Only Pictures and Videos from camera.
vidaljs said:
Whatever recovery u have, Try just putting back UR recovery folded but with only ur backup files when that ff camera worked... ICS and GB.
Click to expand...
Click to collapse
That's the problem, I saved wrong recovery...working one was lost.
I'll try to search older ones today at my home computer, but not sure that it's not JB too...
Hi again, guys. I collected logcat logs from the moment of starting camera to it's death. But I'm not familiar to andoid sources, so, please, anyone can help me to understand, where is the problem?
Code:
I/ActivityManager( 306): START {act=android.intent.action.MAIN cat=[android.int
ent.category.LAUNCHER] flg=0x10200000 cmp=com.android.gallery3d/com.android.came
ra.CameraLauncher u=0} from pid 622
I/ActivityManager( 306): Start proc com.android.gallery3d for activity com.andr
oid.gallery3d/com.android.camera.CameraLauncher: pid=2726 uid=10016 gids={1006,
3003, 1015, 1023, 1028}
I/ActivityThread( 2726): Pub com.android.gallery3d.provider: com.android.gallery
3d.provider.GalleryProvider
V/CameraHolder( 2726): open camera 1
I/CameraService( 134): Opening camera 1
I/CameraHardwareSec( 134): int android::HAL_camera_device_open(const hw_module_
t*, char const*, hw_device_t**): open camera 1
E/SecCamera( 134): initCamera: m_cam_fd(26), m_jpeg_fd(0)
I/SecCamera( 134): Name of input channel[1] is S5KA3DFX
E/SecCamera( 134): initCamera: m_cam_fd2(27)
I/SecCamera( 134): Name of input channel[1] is S5KA3DFX
I/SecCamera( 134): initCamera : initialized
I/SecCamera( 134): Name of input channel[1] is S5KA3DFX
I/CameraHardwareSec( 134): int android::HAL_camera_device_open(const hw_module_
t*, char const*, hw_device_t**): opened camera 1 (0x40ccef90)
I/AwesomePlayer( 134): setDataSource_l('/system/media/audio/ui/camera_click.ogg
')
I/CameraHardwareSec( 134): int android::CameraHardwareSec::previewThreadWrapper
(): starting
I/CameraHardwareSec( 134): int android::CameraHardwareSec::previewThreadWrapper
(): calling mSecCamera->stopPreview() and waiting
W/SecCamera( 134): int android::SecCamera::stopPreview(): doing nothing because
m_flag_camera_start is zero
E/WVMExtractor( 134): IsWidevineMedia not found in libwvm.so
I/AwesomePlayer( 134): setDataSource_l('/system/media/audio/ui/VideoRecord.ogg'
)
E/WVMExtractor( 134): IsWidevineMedia not found in libwvm.so
V/StateManager( 2726): startState class com.android.gallery3d.app.PhotoPage
D/OrientationManager( 2726): lock orientation to portrait
V/camera ( 2726): mSceneMode auto
V/camera ( 2726): Color effect value =none
V/camera ( 2726): autoExposure value =center
V/camera ( 2726): antiBanding value =auto
D/CameraSettings( 2726): Parameters: [camera-mode=0, effect-values=none,mono,neg
ative,sepia, effect=none, exposure-compensation-step=0.5, exposure-compensation=
0, focal-length=0.9, focus-distances=0.20,0.25,Infinity, focus-mode-values=fixed
, focus-mode=fixed, horizontal-view-angle=51.2, jpeg-quality=90, jpeg-thumbnail-
height=120, jpeg-thumbnail-quality=100, jpeg-thumbnail-size-values=160x120,0x0,
jpeg-thumbnail-width=160, max-exposure-compensation=4, min-exposure-compensation
=-4, picture-format-values=jpeg, picture-format=jpeg, picture-size-values=640x48
0, picture-size=640x480, preview-format-values=yuv420sp,yuv420p, preview-format=
yuv420sp, preview-fps-range-values=(7500,30000), preview-fps-range=7500,30000, p
review-frame-rate-values=15, preview-frame-rate=15, preview-size-values=640x480,
320x240,176x144, preview-size=640x480, recording-hint=false, rotation=0, vertica
l-view-angle=39.4, video-frame-format=yuv420p, whitebalance-values=auto,incandes
cent,fluorescent,daylight,cloudy-daylight, whitebalance=auto]
V/camera ( 2726): mSceneMode auto
V/camera ( 2726): Color effect value =none
V/camera ( 2726): autoExposure value =center
V/camera ( 2726): antiBanding value =auto
D/CameraSettings( 2726): Parameters: [camera-mode=0, effect-values=none,mono,neg
ative,sepia, effect=none, exposure-compensation-step=0.5, exposure-compensation=
0, focal-length=0.9, focus-distances=0.20,0.25,Infinity, focus-mode-values=fixed
, focus-mode=fixed, horizontal-view-angle=51.2, jpeg-quality=90, jpeg-thumbnail-
height=120, jpeg-thumbnail-quality=100, jpeg-thumbnail-size-values=160x120,0x0,
jpeg-thumbnail-width=160, max-exposure-compensation=4, min-exposure-compensation
=-4, picture-format-values=jpeg, picture-format=jpeg, picture-size-values=640x48
0, picture-size=640x480, preview-format-values=yuv420sp,yuv420p, preview-format=
yuv420sp, preview-fps-range-values=(7500,30000), preview-fps-range=7500,30000, p
review-frame-rate-values=15, preview-frame-rate=15, preview-size-values=640x480,
320x240,176x144, preview-size=640x480, recording-hint=false, rotation=0, vertica
l-view-angle=39.4, video-frame-format=yuv420p, whitebalance-values=auto,incandes
cent,fluorescent,daylight,cloudy-daylight, whitebalance=auto]
V/camera ( 2726): startPreview
E/WVMExtractor( 134): IsWidevineMedia not found in libwvm.so
I/Thumbnail( 2726): Fail to load bitmap. java.io.FileNotFoundException: /data/da
ta/com.android.gallery3d/files/last_thumb: open failed: ENOENT (No such file or
directory)
D/CameraStorage( 2726): External storage state=mounted
D/libEGL ( 2726): loaded /vendor/lib/egl/libEGL_POWERVR_SGX540_120.so
D/libEGL ( 2726): loaded /vendor/lib/egl/libGLESv1_CM_POWERVR_SGX540_120.so
E/SecCamera( 134): ERR(int android::fimc_v4l2_streamon(int)):VIDIOC_STREAMON fa
iled
E/SecCamera( 134): int android::SecCamera::startPreview()::748 fail. errno: I/O
error, m_camera_id = 1
E/CameraHardwareSec( 134): ERR(android::status_t android::CameraHardwareSec::st
artPreviewInternal()):Fail on mSecCamera->startPreview()
I/CameraHardwareSec( 134): int android::CameraHardwareSec::previewThreadWrapper
(): return from wait
I/CameraHardwareSec( 134): int android::CameraHardwareSec::previewThreadWrapper
(): calling mSecCamera->stopPreview() and waiting
W/SecCamera( 134): int android::SecCamera::stopPreview(): doing nothing because
m_flag_camera_start is zero
I/CameraHardwareSec( 134): int android::CameraHardwareSec::previewThreadWrapper
(): return from wait
I/CameraHardwareSec( 134): int android::CameraHardwareSec::previewThreadWrapper
(): exiting
W/SecCamera( 134): int android::SecCamera::stopPreview(): doing nothing because
m_flag_camera_start is zero
W/SecCamera( 134): int android::SecCamera::stopRecord(): doing nothing because
m_flag_record_start is zero
I/SecCamera( 134): DeinitCamera: m_cam_fd(26)
I/SecCamera( 134): DeinitCamera: m_cam_fd2(27)
E/CameraHardwareSec( 134): preview window is NULL!
I/CameraService( 134): Destroying camera 1
I/CameraHardwareSec( 134): int android::HAL_camera_device_close(hw_device_t*)
I/SecCamera( 134): DeinitCamera : already deinitialized
W/dalvikvm( 2726): threadid=13: thread exiting with uncaught exception (group=0x
415f0300)
E/AndroidRuntime( 2726): FATAL EXCEPTION: Camera Handler Thread
E/AndroidRuntime( 2726): java.lang.RuntimeException: startPreview failed
E/AndroidRuntime( 2726): at android.hardware.Camera.startPreview(Native M
ethod)
E/AndroidRuntime( 2726): at com.android.camera.CameraManager$CameraHandle
r.handleMessage(CameraManager.java:128)
E/AndroidRuntime( 2726): at android.os.Handler.dispatchMessage(Handler.ja
va:99)
E/AndroidRuntime( 2726): at android.os.Looper.loop(Looper.java:137)
E/AndroidRuntime( 2726): at android.os.HandlerThread.run(HandlerThread.ja
va:60)
W/AudioFlinger( 134): session id 34 not found for pid 134
W/AudioFlinger( 134): session id 35 not found for pid 134
W/ActivityManager( 306): Force finishing activity com.android.gallery3d/com.a
ndroid.camera.CameraLauncher
D/libEGL ( 2726): loaded /vendor/lib/egl/libGLESv2_POWERVR_SGX540_120.so
D/OpenGLRenderer( 2726): Enabling debug mode 0
D/ActivityBase( 2726): set CameraRelativeFrame as Rect(0, 0 - 480, 640)
D/PhotoView( 2726): compensation = 0, CameraRelativeFrame = Rect(0, 0 - 480, 640
), mCameraRect = Rect(0, 0 - 480, 640)
I/GalleryEGLConfigChooser( 2726): Config chosen: R5 G6 B5 A0 D24 S8 ID7 CAVEAT12
344
I/GLRootView( 2726): onSurfaceChanged: 480x800, gl10: com.google.android.gles_jn
[email protected]
I/GLRootView( 2726): layout content pane 480x800 (compensation 0)
D/PhotoView( 2726): compensation = 0, CameraRelativeFrame = Rect(0, 0 - 480, 640
), mCameraRect = Rect(0, 0 - 480, 640)
D/dalvikvm( 2726): GC_FOR_ALLOC freed 873K, 30% free 5885K/8387K, paused 55ms, t
otal 57ms
I/dalvikvm-heap( 2726): Grow heap (frag case) to 14.594MB for 635812-byte alloca
tion
I/ActivityManager( 306): Displayed com.android.gallery3d/com.android.camera.Cam
eraLauncher: +1s240ms (total +33s607ms)
W/InputMethodManagerService( 306): Focus gain on non-focused client com.android
[email protected] (uid=10016 pid=2726)
I/ActivityManager( 306): Process com.android.deskclock (pid 2377) has died.
W/ActivityManager( 306): Activity pause timeout for ActivityRecord{419e0178 com
.android.gallery3d/com.android.camera.CameraLauncher}
D/dalvikvm( 755): GC_EXPLICIT freed 510K, 59% free 3465K/8387K, paused 60ms+4ms
, total 630ms
D/SiMiClock( 1293): onUpdate
D/SiMiClock( 1293): onUpdate - 5
D/dalvikvm( 1293): GC_CONCURRENT freed 1809K, 72% free 2423K/8387K, paused 10ms+
49ms, total 145ms
I/Process ( 2726): Sending signal. PID: 2726 SIG: 9
W/InputMethodManagerService( 306): Window already focused, ignoring focus gain
of: [email protected] attribute=n
ull
I/WindowState( 306): WIN DEATH: Window{41be2c20 SurfaceView paused=false}
I/ActivityManager( 306): Process com.android.gallery3d (pid 2726) has died.
I/WindowState( 306): WIN DEATH: Window{41985468 com.android.gallery3d/com.andro
id.camera.CameraLauncher paused=false}
My current ROM is CNA 3.6.6. Only front face camera crashes, but even in factory roms.
I have the same problem : back camera works great, but when i switch to front camera : "unfortunately, Gallery has stopped" and i have to go to settings, gallery, force stop and clear data.
I tried the stock rom and now i am running on 4.3 Illusion-v2.5.alpha-UNOFFICIAL-crespo , with the good gapps.
I have tried all the previous solutions from this topic .... but no luck.
dan_paul said:
I have the same problem : back camera works great, but when i switch to front camera : "unfortunately, Gallery has stopped" and i have to go to settings, gallery, force stop and clear data.
I tried the stock rom and now i am running on 4.3 Illusion-v2.5.alpha-UNOFFICIAL-crespo , with the good gapps.
I have tried all the previous solutions from this topic .... but no luck.
Click to expand...
Click to collapse
I changed many roms from time I wrote it, no luck, I think it's a hardware problem...(((
I have the same problem... I have tired stock roms as well as many custom roms but failed... Is there any kernel to fix this issue?
Sent from my Nexus S using XDA Premium 4 mobile app
Related
In the past few days, I installed JFv1.31, wiped the phone, moved all my caches to the SD card, set up the phone&sdcard to run apps off the SD card, and installed a BUNCH of apps. Everything works great, except, oh right, the phone.
Whenever I get or try to make a call, the phone app crashes, with the error message 'The process android.process.acore has stopped unexpectedly. Please try again.'
Is there any reasonably simple way for me to figure out what's making the process crash? I'd really rather not have to rewipe the phone and redo everything I did.
Probably because you are messing with the filesystem. While it make work for some moving the cache and apps to the SD card has unknown longterm effects.
You may have just found the reason why most of us read the warnings and decided not to do such a risky procedure.
neoobs said:
Probably because you are messing with the filesystem. While it make work for some moving the cache and apps to the SD card has unknown longterm effects.
You may have just found the reason why most of us read the warnings and decided not to do such a risky procedure.
Click to expand...
Click to collapse
.......Yeah, that doesn't really make any logical sense. Linux doesn't care where any given part of the filesystem is, and if something works in the short term, then it works in the long term. It's not going to degrade on it's own. I'm reasonably sure that the problem is some kind of conflict with one of the apps I installed, but I have no idea how android is logging things, so no idea what log to check.
Plus, none of the core system apps are moved to the SD card, just the stuff installed off the market. And considering that reversing the process is ridiculously easy, it's not really a risky procedure unless you don't know what the commands do AND aren't careful about copying them over.
If you know what log to check to see what's happening immediately before the crash, great, let me know. If all you've got is 'zomg, I don't understand the filesystem and find it scary' then you're no help to me, but thanks for the....doom and gloom I guess.
And, ya know, if there is a problem with moving apps? (I'm sure the problem isn't moving caches, I'd had that done for months) How do you think the problem will get FOUND without people trying it, and then reporting on and troubleshooting the errors? Saying 'You had a problem, clearly you shouldn't have tried it' isn't going to lead to things getting better developed and more stable.
Some info on android.process.acore:
http://groups.google.com/group/android-platform/browse_thread/thread/87f075abebf2a557
You might also want to look for entries in logcat.
heldc said:
.......Yeah, that doesn't really make any logical sense. Linux doesn't care where any given part of the filesystem is, and if something works in the short term, then it works in the long term. It's not going to degrade on it's own. I'm reasonably sure that the problem is some kind of conflict with one of the apps I installed, but I have no idea how android is logging things, so no idea what log to check.
Plus, none of the core system apps are moved to the SD card, just the stuff installed off the market. And considering that reversing the process is ridiculously easy, it's not really a risky procedure unless you don't know what the commands do AND aren't careful about copying them over.
If you know what log to check to see what's happening immediately before the crash, great, let me know. If all you've got is 'zomg, I don't understand the filesystem and find it scary' then you're no help to me, but thanks for the....doom and gloom I guess.
And, ya know, if there is a problem with moving apps? (I'm sure the problem isn't moving caches, I'd had that done for months) How do you think the problem will get FOUND without people trying it, and then reporting on and troubleshooting the errors? Saying 'You had a problem, clearly you shouldn't have tried it' isn't going to lead to things getting better developed and more stable.
Click to expand...
Click to collapse
Excuse me?
I didn't give attitude just the fact that messing with the filesystem can cause errors. Many people have had SD card issues, SD card mounting/unmounting, corruption and just plain not working for various reasons.
So far we don't have enough information to find the problem. But these problems can cause other problems. If you keep your cache and apps on a SD card and it is unmounted randomly, or becomes corrupt, or for some reason just plain stops working this would cause corruption through the entire system.
If you used this guide http://forum.xda-developers.com/showthread.php?t=468959 then you have infact moved system data. Since the system apps do push and pull files from the /data/app* directories.
It is hard to figure out what logs you would need to check if you have moved things. The easiest way is to use ddms since that shows everything that has happened and is happening. But this may not help you. Give it a shot and post the part of the log in red and we can all see what is causing it.
Don't get mad that the problem might be something you did. We are trying to help. I gave you my suggestion, revert back to normal and stop trying to mess with the filesystem. If you don't like it that is great but that doesn't mean I didn't help.
neoobs said:
Don't get mad that the problem might be something you did. We are trying to help. I gave you my suggestion, revert back to normal and stop trying to mess with the filesystem. If you don't like it that is great but that doesn't mean I didn't help.
Click to expand...
Click to collapse
I'm not mad that the problem is something I did, I'm sure it is, that's why I listed what hacks I'd applied. I'm annoyed at the attitude you seem to have toward 'if there's a problem, that means you shouldn't have tried to mod in the first place.' That's not helpful, it just leads to people not trying things, not finding bugs, not troubleshooting, and not advancing the knowledge of how to work with this phone. Sorry to snap about it, it's just a pet peeve of mine, people trying to trouble shoot stuff and getting told 'oh that's risky you shouldn't have done it in the first place'.
I mean, the entire xda forum is for hacking and modding and developing. When someone tries a hack in full knowledge of the risks they run, and then they have a problem, come looking for trouble shooting help, and get told 'you shouldn't have tried the hack cos it's risky' that's just....against the whole idea of hacking your hardware!
did you run the sh script to change your app's caches ? if you did, please provide it here and we will see which lines you shouldn't run
I had the same exact problem. I had to wipe my phone and now everything runs fine again, for now.
namsir said:
did you run the sh script to change your app's caches ? if you did, please provide it here and we will see which lines you shouldn't run
Click to expand...
Click to collapse
I ran a slightly modded script. Maybe that is the problem, I did the cache moving manually when I did it before, and used the script this time.
Code:
chmod 0777 /data/local/bin/transfer.sh
mkdir /sdcard/cache
mkdir /sdcard/cache/files
cd /data/data/com.google.android.apps.maps
mkdir /sdcard/cache/files/maps
busybox cp -a files /sdcard/cache/files/maps
rm -R files
ln -s /sdcard/cache/files/maps/files files
cd /data/data/com.android.browser/cache
rm -R webviewCache
mkdir /sdcard/cache/webviewCache
ln -s /sdcard/cache/webviewCache webviewCache
cd /data/data/com.google.android.street
rm -R cache
mkdir /sdcard/cache/streetCache
ln -s /sdcard/cache/streetCache cache
cd /data/data/com.android.vending
rm -R cache
mkdir /sdcard/cache/marketCache
ln -s /sdcard/cache/marketCache cache
heldc said:
I'm not mad that the problem is something I did, I'm sure it is, that's why I listed what hacks I'd applied. I'm annoyed at the attitude you seem to have toward 'if there's a problem, that means you shouldn't have tried to mod in the first place.' That's not helpful, it just leads to people not trying things, not finding bugs, not troubleshooting, and not advancing the knowledge of how to work with this phone. Sorry to snap about it, it's just a pet peeve of mine, people trying to trouble shoot stuff and getting told 'oh that's risky you shouldn't have done it in the first place'.
I mean, the entire xda forum is for hacking and modding and developing. When someone tries a hack in full knowledge of the risks they run, and then they have a problem, come looking for trouble shooting help, and get told 'you shouldn't have tried the hack cos it's risky' that's just....against the whole idea of hacking your hardware!
Click to expand...
Click to collapse
I understand.
This goes beyond hacking thou. This has been said by quite a few that this just isn't good. It isn't stable and we aren't advancing it. Basically this has become a stale hack that will not be improved upon because there is no method to improve it. It is a hack that is unstable and sloppy. No offense to the finder but it is a crude fix.
Ok, I ran ddms, and made it crash. This is the output before I hit the call button, through the crash message and me hitting force close. I don't code, so this means next to nothing to me. I think I am going to be lazy tho, and just wipe. I'd like a working phone before going out tonight. Maybe someone can find something of some use in the log tho.
Code:
01-19 19:39:10.102: DEBUG/dalvikvm(90): GC freed 1541 objects / 74928 bytes in 96ms
01-19 19:39:22.522: INFO/ActivityManager(57): Starting activity: Intent { action=android.intent.action.CALL_BUTTON flags=0x10000000 comp={com.android.contacts/com.android.contacts.DialtactsActivity} }
01-19 19:39:22.942: DEBUG/dalvikvm(231): GC freed 2646 objects / 156288 bytes in 92ms
01-19 19:39:23.322: ERROR/ActivityThread(231): Failed to find provider info for call_log
01-19 19:39:23.332: ERROR/ActivityThread(231): Failed to find provider info for call_log
01-19 19:39:23.332: WARN/dalvikvm(231): threadid=19: thread exiting with uncaught exception (group=0x40013e28)
01-19 19:39:23.332: ERROR/AndroidRuntime(231): Uncaught handler: thread AsyncQueryWorker exiting due to uncaught exception
01-19 19:39:23.342: ERROR/AndroidRuntime(231): java.lang.IllegalArgumentException: Unknown URI content://call_log/calls
01-19 19:39:23.342: ERROR/AndroidRuntime(231): at android.content.ContentResolver.update(ContentResolver.java:409)
01-19 19:39:23.342: ERROR/AndroidRuntime(231): at android.content.AsyncQueryHandler$WorkerHandler.handleMessage(AsyncQueryHandler.java:89)
01-19 19:39:23.342: ERROR/AndroidRuntime(231): at android.os.Handler.dispatchMessage(Handler.java:88)
01-19 19:39:23.342: ERROR/AndroidRuntime(231): at android.os.Looper.loop(Looper.java:123)
01-19 19:39:23.342: ERROR/AndroidRuntime(231): at android.os.HandlerThread.run(HandlerThread.java:60)
01-19 19:39:23.382: INFO/Process(57): Sending signal. PID: 231 SIG: 3
01-19 19:39:23.382: INFO/dalvikvm(231): threadid=7: reacting to signal 3
01-19 19:39:23.512: VERBOSE/DumpStateReceiver(57): Running: /system/bin/dumpcrash
01-19 19:39:23.522: INFO/dalvikvm(231): Wrote stack trace to '/data/anr/traces.txt'
01-19 19:39:23.752: INFO/ActivityManager(57): Displayed activity com.android.contacts/.DialtactsActivity: 1229 ms
01-19 19:39:23.922: INFO/DumpStateReceiver(57): Finished: 2282 bytes read; status 0
01-19 19:39:24.002: INFO/DumpStateReceiver(57): Added state dump to 1 crashes
01-19 19:39:28.363: INFO/Process(231): Sending signal. PID: 231 SIG: 9
01-19 19:39:28.393: INFO/ActivityManager(57): Process android.process.acore (pid 231) has died.
01-19 19:39:28.393: INFO/WindowManager(57): WIN DEATH: Window{431088a8 com.android.launcher/com.android.launcher.Launcher}
01-19 19:39:28.393: INFO/WindowManager(57): WIN DEATH: Window{4323db80 com.android.contacts/com.android.contacts.DialtactsActivity}
01-19 19:39:28.402: INFO/ActivityThread(241): Removing dead content provider: im
01-19 19:39:28.412: INFO/ActivityManager(57): Killing app com.google.process.gapps (pid 241) because provider com.android.providers.im.ImProvider is in dying process android.process.acore
01-19 19:39:28.412: INFO/Process(57): Sending signal. PID: 241 SIG: 9
01-19 19:39:28.482: INFO/ActivityManager(57): Start proc android.process.acore for activity com.android.launcher/.Launcher: pid=272 uid=10014 gids={3003}
01-19 19:39:28.482: INFO/ActivityManager(57): Process com.google.process.gapps (pid 241) has died.
01-19 19:39:28.492: WARN/ActivityManager(57): Scheduling restart of crashed service com.google.android.apps.gtalkservice/com.google.android.gtalkservice.service.GTalkService in 5000ms
01-19 19:39:28.582: INFO/jdwp(272): received file descriptor 10 from ADB
01-19 19:39:28.712: INFO/ActivityThread(272): Publishing provider im: com.android.providers.im.ImProvider
01-19 19:39:28.782: INFO/ActivityThread(272): Publishing provider com.android.googlesearch.SuggestionProvider: com.android.googlesearch.SuggestionProvider
01-19 19:39:29.092: DEBUG/dalvikvm(272): GC freed 1702 objects / 115144 bytes in 96ms
01-19 19:39:29.252: DEBUG/dalvikvm(272): GC freed 421 objects / 30424 bytes in 76ms
01-19 19:39:29.552: INFO/ActivityManager(57): Displayed activity com.android.launcher/.Launcher: 1123 ms
01-19 19:39:33.512: INFO/ActivityManager(57): Start proc com.google.process.gapps for service com.google.android.apps.gtalkservice/com.google.android.gtalkservice.service.GTalkService: pid=281 uid=10000 gids={3003}
01-19 19:39:33.562: INFO/jdwp(281): received file descriptor 10 from ADB
01-19 19:39:33.652: INFO/ActivityThread(281): Publishing provider gmail-ls: com.google.android.providers.gmail.MailProvider
01-19 19:39:34.312: DEBUG/dalvikvm(57): GC freed 15232 objects / 765512 bytes in 216ms
01-19 19:39:35.232: DEBUG/dalvikvm(281): GC freed 4466 objects / 359648 bytes in 118ms
01-19 19:39:35.452: INFO/gmail-ls(281): MailCore.setConfig
01-19 19:39:35.452: DEBUG/gmail-ls(281): MailCore.setConfig: included: 9/^r
01-19 19:39:35.452: DEBUG/gmail-ls(281): MailCore.setConfig: partial: 2/^f
01-19 19:39:35.452: DEBUG/gmail-ls(281): MailCore.setConfig: partial: 3/^i
01-19 19:39:35.452: DEBUG/gmail-ls(281): MailCore.setConfig: partial: 31/info
01-19 19:39:35.462: DEBUG/gmail-ls(281): MailCore.setConfig: partial: 11/lj
01-19 19:39:35.462: DEBUG/gmail-ls(281): MailCore.setConfig: partial: 12/mysshop
01-19 19:39:35.462: DEBUG/gmail-ls(281): MailCore.setConfig: partial: 35/work
01-19 19:39:35.462: INFO/gmail-ls(281): MailCore.setConfig
01-19 19:39:35.462: DEBUG/gmail-ls(281): MailCore.setConfig: included: 9/^r
01-19 19:39:35.472: DEBUG/gmail-ls(281): MailCore.setConfig: partial: 2/^f
01-19 19:39:35.472: DEBUG/gmail-ls(281): MailCore.setConfig: partial: 3/^i
01-19 19:39:35.472: DEBUG/gmail-ls(281): MailCore.setConfig: partial: 31/info
01-19 19:39:35.472: DEBUG/gmail-ls(281): MailCore.setConfig: partial: 11/lj
01-19 19:39:35.472: DEBUG/gmail-ls(281): MailCore.setConfig: partial: 12/mysshop
01-19 19:39:35.472: DEBUG/gmail-ls(281): MailCore.setConfig: partial: 35/work
01-19 19:39:35.602: DEBUG/gmail-ls(281): Purging old attachments
I had trouble with acore crashing when I restored my contacts using mybackup. Deleting all of my contacts from the phone letting it resync them automatically fixed the problem.
It is trying to find something that isn't there, looks like call logs. The log to look at is /data/anr/traces.txt but you can't get to taht even with root.
i just had this same problem and all i did was move my caches to the sdcard and thats it. i understand a little of what i did in the process but i know i implemented the hacks that are tried and tested and known to not be able to brick ur g1. The most i have done with the contacts and call logs is applying the carbon glow theme to my g1 and thats it so could it be something with adding themes onto the g1 and something that might not have been done right in the zip files. im not saying that the person did something wrong with his theme but maybe themes just dont work fully in some parts of the os.
heldc said:
In the past few days, I installed JFv1.31, wiped the phone, moved all my caches to the SD card, set up the phone&sdcard to run apps off the SD card, and installed a BUNCH of apps. Everything works great, except, oh right, the phone.
Whenever I get or try to make a call, the phone app crashes, with the error message 'The process android.process.acore has stopped unexpectedly. Please try again.'
Is there any reasonably simple way for me to figure out what's making the process crash? I'd really rather not have to rewipe the phone and redo everything I did.
Click to expand...
Click to collapse
have u maybe installed mono after the install.. for some reason i think that messed me up the first time and time after that..
i installed mono for a short time and then unistalled it
I'm having the same thing happening on my g1, except it happens after i hang up a call. After it force closes, it seems to reload after a few seconds, and brings me back to the home screen. There's really no problems I can see, aside from the force close warning and the 5 second lag time to reload it, but it would be nice to get to the bottom of this. I can't remember if this happened before I moved the caches to the storage card or not, but I will perform a wipe and see if it continues. Can we confirm that this is due to the relocation of the cache?
Hello everybody,
I keep getting this error:
SORRY! The process com.google.process.gapps hast stopped unexpectedly. Please try again.
I can not acces my contact, gmail or the market.
It started yesterday but i didn't do anything special to have caused this error. Does anyone have an idea what to do?
Thanks for helping.
G1Dennis said:
Hello everybody,
I keep getting this error:
SORRY! The process com.google.process.gapps hast stopped unexpectedly. Please try again.
It started yesterday but i didn't do anything special to have caused this error. Does anyone have an idea what to do?
Thanks for helping.
Click to expand...
Click to collapse
gmail error, I believe... uncheck autosync and recheck it and manually sync all. if that fails... remove battery while phone is on and sim. boot up and if that fails you may want to clear your mail via pc/mac while phone if off. Also, you can change the amount of days to sync mail and that should do it. Sorry I can't be more specific... that error happened to me months ago and I can't remember which one worked specifically.
Didn't work
Now i get a second error:
Your suggestions did not work yet.
SORRY!
The proces com.google.process.acore has stopped unexpectedly. Please try again.
Have you used any methods (symlink or the new one) to move your apps and cache to the SD card? If so, I suggest undoing the cache move and seeing if that fixed the problem.
What build are you coming from?
I ran into that yesterday. A wipe was the only thing that fixed it.
G1Dennis said:
Hello everybody,
I keep getting this error:
SORRY! The process com.google.process.gapps hast stopped unexpectedly. Please try again.
I can not acces my contact, gmail or the market.
It started yesterday but i didn't do anything special to have caused this error. Does anyone have an idea what to do?
Thanks for helping.
Click to expand...
Click to collapse
definitely need more info .. what processes are done .. have you tried moving /data/data back to the phone? etc
this happened to me on saturday when i wasn playing around with the file system. it could simply be some corrupted files in dalvik-cache. try rm /data/dalvik-cache/* and then reboot (must do this thru adb, because everything will crash soon after rm). the phone will take sometime to recreate the files and then it should work fine.
edit:
if you're using a2sd, you should try move dalvik-cache back first.
sometimes a single app at startup will cause the "acore" crash. A couple of themes did that also. Yeah, we definately need more info... build name and number, plus a2sd or regular, theme or no theme, etc.
I was getting that same error and a wipe didn't correct it, my best guess was that the google apps file that contains the login info was still on my memory card from when i had moved /data to sd, and was confilicting with the same file on the phones memory. After deleting that file off the sd and a reboot it hasn't popped up since.
pgiuoco said:
I was getting that same error and a wipe didn't correct it, my best guess was that the google apps file that contains the login info was still on my memory card from when i had moved /data to sd, and was confilicting with the same file on the phones memory. After deleting that file off the sd and a reboot it hasn't popped up since.
Click to expand...
Click to collapse
and how did you do that, and which file was it?
ok so i am havving a issue with themes and process.gaps..
ive tried just about everytheme and non seem to like my gmail account...
ive wiped..fix_permission..cleared cache and everything...i try to open my data sync in my data sync. in my setting (menu>setting>data sync) it just opens then closes right off the back.. also my gmail wont sync when i do i manually!.. herre is my log cat!
anyone please help!!!!!!!!
D/dalvikvm( 234): GC freed 4310 objects / 215352 bytes in 127ms
I/ActivityManager( 144): Starting activity: Intent { act=android.intent.action.
MAIN cat=[android.intent.category.LAUNCHER] flg=0x10200000 cmp=com.google.androi
d.gm/.ConversationListActivityGmail }
I/ActivityManager( 144): Start proc com.google.android.gm for activity com.goog
le.android.gm/.ConversationListActivityGmail: pid=736 uid=10036 gids={3003}
I/ActivityThread( 736): Publishing provider com.google.android.gm.attachmentspr
eviews: com.google.android.gm.AttachmentPreviewProvider
I/ActivityThread( 736): Publishing provider com.google.android.gmail.Suggestion
Provider: com.google.android.gm.SuggestionsProvider
I/ActivityThread( 736): Publishing provider com.google.android.gm.status: com.g
oogle.android.gm.SenderStatusProvider
I/ActivityManager( 144): Starting activity: Intent { act=android.intent.action.
MAIN cat=[android.intent.category.LAUNCHER] flg=0x2800000 cmp=com.google.android
.gm/.ConversationListActivity }
V/Gmail ( 736): onCreate(), id=com.google.android.gm.ConversationListActivity
@43679d08
I/ActivityManager( 144): Starting activity: Intent { flg=0x2000000 cmp=com.goog
le.android.gm/.WaitActivity (has extras) }
I/ActivityManager( 144): Displayed activity com.google.android.gm/.Conversation
ListActivity: 88 ms (total 539 ms)
W/InputManagerService( 144): Starting input on non-focused client com.android.i
nternal.v[email protected] (uid=10036 pid=736)
W/InputManagerService( 144): Client not active, ignoring focus gain of: com.and
[email protected]
W/InputManagerService( 144): Window already focused, ignoring focus gain of: co
[email protected]
D/ForecastProvider( 510): query() with uri=content://com.androidapps.widget.wea
ther2/appwidgets/5
D/ForecastProvider( 510): query() with uri=content://com.androidapps.widget.wea
ther2/appwidgets/5
D/dalvikvm( 510): GC freed 853 objects / 448232 bytes in 80ms
I/ActivityManager( 144): Process com.google.android.gm (pid 736) has died.
D/dalvikvm( 234): GC freed 3207 objects / 163008 bytes in 132ms
I/ActivityManager( 144): Starting activity: Intent { act=android.intent.action.
MAIN cat=[android.intent.category.HOME] flg=0x10200000 cmp=com.android.launcher/
.Launcher }
I/ActivityManager( 144): Starting activity: Intent { act=android.settings.SETTI
NGS flg=0x10200000 cmp=com.android.settings/.Settings }
I/ActivityManager( 144): Starting activity: Intent { cmp=com.android.providers.
subscribedfeeds/com.android.settings.SyncSettings }
W/InputManagerService( 144): Starting input on non-focused client android.view.
[email protected] (uid=1000 pid=144)
W/InputManagerService( 144): Client not active, ignoring focus gain of: android
[email protected]
W/InputManagerService( 144): Window already focused, ignoring focus gain of: co
[email protected]
I/ActivityManager( 144): Starting activity: Intent { cmp=com.android.providers.
subscribedfeeds/com.android.settings.SyncSettings }
W/InputManagerService( 144): Starting input on non-focused client android.view.
[email protected] (uid=1000 pid=144)
W/InputManagerService( 144): Client not active, ignoring focus gain of: android
[email protected]
W/InputManagerService( 144): Window already focused, ignoring focus gain of: co
[email protected]
I/ActivityManager( 144): Starting activity: Intent { act=android.intent.action.
MAIN cat=[android.intent.category.HOME] flg=0x10200000 cmp=com.android.launcher/
.Launcher }
W/InputManagerService( 144): Starting input on non-focused client com.android.i
[email protected] (uid=1000 pid=699)
Got the error as well. Fixed it by going into "Settings>Manage Applications" and selecting Google Apps and Clearing Data and then do the same for GMail and any other Google App you are having a problem with. After this you will have to re-enter your account info again and everything should sync back up without problem. Hope this helps. try it it will work just wipe the data from all google apps
Hello folks. Here's a quick and dirty way to solve your problems:
I started to get the com.google.process.gapps and the com.htc.bg FC's a few days back. And I didn't have a clue why. After 2 days spent doing logcats and stuff... In the end i noticed that my google sync account and the facebook & facebook for htc sense account gave error messages when sync-ing contacts. So... I cleared all data for those programs (go to settings - applications - manage applications). Removed the google sync and facebook sync accounts. Erased all of the contacts from my phone (afer previously backing them up to the sd).
And... reboot the phone, configure the sync accounts for google and facebook, do a full sync with contacts... and afterwards restore only the phone contacts back... Re-link the contacts and everything is running perfectly right now.
Hope it helps.
same problem traced to my calendar
diaz2611 said:
Got the error as well. Fixed it by going into "Settings>Manage Applications" and selecting Google Apps and Clearing Data and then do the same for GMail and any other Google App you are having a problem with. After this you will have to re-enter your account info again and everything should sync back up without problem. Hope this helps. try it it will work just wipe the data from all google apps
Click to expand...
Click to collapse
This worked for me. I traced the problem to my calendar - it wouldn't sync. I'm not sure how it 'got broke'. Opening the Apps management and stopping anything dealing with the calendar and clearing the cache did the trick.
Running Apex 1.4 - BWC theme DX
com.google.process.gapps stopped unexpectedly
I have tried tracing the problem.
My conclusion.
There is no need to reboot or hard reset.
It will not solve the problem.
The problem is hidden calls that are being made by certain applications
especially the Market. Whenever you enter market and try a new app, one of the hidden call is made for screen capture.
And the captured screen is then sent via network connection to somewhere.
This procedure call seems to create the error.
Either screen capture fails or the network connection fails.
The procedure call stays in memory and is activated at variable interval based on network connection status.
During this activation and subsequent failure the com.google.process.gapps stops.
I simply went into the running services and stopped the mobile tracking service and screen capture service (if it is active)
The android becomes stable after that.
Frequent use of Task Manager to clear level 1 and 2 memory also provides stability after use of Market.
Removed...
I, for the life of me, can't get the Evo 4G to start the Netflix app correctly. It shows a white screen, and then after a bit of time it throws a message saying
"Error : Please make sure the device's date and time settings are updated to the current date."
It's operating on the auto-time, and no matter what I do - reboot, re-install Netflix, etc - I still get that error. I can see it transferring data - so I am not sure what this means. I even tried flashing back to my stock ROM, the backup I have right after I rooted the phone - and it still doesn't do it (I was running Azrael's 4.0 sense rom prior).
I've seen other folks mention this - has anyone else run into this or figured out a resolution?
+1 same issue here running Calkulin 1.8
Sent from my PC36100 using XDA App
It seems like each phone has a different issue. I don't have an evo, but I'm working on ironing out the issues, unless Netflix beats me to it. I haven't seen this issue yet. Could you provide a logcat from right before starting Netflix up.
Sent from my HERO200 using XDA App
I was having the same problem with my wife's Evo including the error message. I went and resynced everything and after that Netflix started working. Hope that helps.
Mine plays but has no sound?
Sent from my PC36100 using Tapatalk
Cleared cache and dalvik and now it works....
Sent from my PC36100 using Tapatalk
I'm having the same issue as the original poster -- re-installed, rebooted, cleared cache, still no luck. Novice smartphone user, so everything is original equipment, no rooting, etc.
unCoRrUpTeD said:
It seems like each phone has a different issue. I don't have an evo, but I'm working on ironing out the issues, unless Netflix beats me to it. I haven't seen this issue yet. Could you provide a logcat from right before starting Netflix up.
Sent from my HERO200 using XDA App
Click to expand...
Click to collapse
I'll try - gimme today to fiddle with it, never messed with logcat, so I'll need to learn what to do with that.
unCoRrUpTeD said:
It seems like each phone has a different issue. I don't have an evo, but I'm working on ironing out the issues, unless Netflix beats me to it. I haven't seen this issue yet. Could you provide a logcat from right before starting Netflix up.
Sent from my HERO200 using XDA App
Click to expand...
Click to collapse
Attached is a ZIP that has logfiles for just netflix activity from starting it up to closing it out, as well as another file that has all entries during that same time period. Also, here's the logs surrounding Netflix:
Code:
Process Monitor Widget (logcat)
===============================
Process Netflix(com.netflix.mediaclient)
D/08:32:22.469 GC_EXPLICIT freed 89 objects / 4456 bytes in 78ms
D/08:32:22.139 GC_EXPLICIT freed 1826 objects / 358504 bytes in 104ms
D/08:32:17.269 GC_FOR_MALLOC freed 9684 objects / 414472 bytes in 35ms
D/08:32:11.769 GC_FOR_MALLOC freed 4151 objects / 506824 bytes in 46ms
D/08:32:06.029 GC_FOR_MALLOC freed 5213 objects / 342464 bytes in 32ms
D/08:32:00.429 GC_FOR_MALLOC freed 33 objects / 1352 bytes in 95ms
D/08:31:57.809 GC_EXPLICIT freed 431 objects / 24816 bytes in 30ms
D/08:31:57.659 GC_EXPLICIT freed 2834 objects / 194272 bytes in 42ms
D/08:31:55.179 queueRequest with mProxyHost=null for https://uiboot.netflix.com/apps/mobileui/upgrade_policy?v=2.0&e=NFANDROID1-HTC==PC36100S-44533132&device_type=NFANDROID1-&certification_version=1.2.0%20build%20819145-1.2.0-102
D/08:31:55.179 setProxyConfig mProxyHost=null
D/08:31:55.179 queueRequest to set proxy
D/08:31:55.179 [JWebCoreJavaBridge::resume] >> do resume
D/08:31:55.159 GC_FOR_MALLOC freed 2666 objects / 342392 bytes in 30ms
D/08:31:55.069 Settings::setMixedPluginEnabled 1
D/08:31:55.069 Settings::setMixedPluginEnabled 1
D/08:31:55.069 Settings::setMixedPluginEnabled 1
D/08:31:55.059 Settings::setMixedPluginEnabled 1
I/08:31:55.049 PluginManager::getPluginDirectories target:/data/data/com.adobe.flashplayer/lib
I/08:31:55.049 PluginManager::getPluginDirectories add:/system/lib/
I/08:31:55.039 PluginManager::getPluginDirectories target:/data/data/com.htc.flashliteplugin/lib
E/08:31:55.039 CheckOMX drm.play is not available done
E/08:31:55.039 CheckOMX drm.play is not available
I/08:31:55.039 listNode return 38
I/08:31:55.029 OMX interface is valid
I/08:31:55.029 Got IMediaPlayerService interface
I/08:31:55.029 Got IBinder interface to media.player
I/08:31:55.029 PluginManager::getPluginDirectories
I/08:31:55.009 Got IServiceManager interface
D/08:31:55.009 Shared lib '/data/data/com.netflix.mediaclient/lib/libnetflixmp_jni.so' already loaded in same CL 0x4656e988
D/08:31:55.009 Trying to load lib /data/data/com.netflix.mediaclient/lib/libnetflixmp_jni.so 0x4656e988
D/08:31:55.009 Added shared lib /data/data/com.netflix.mediaclient/lib/libnetflixmp_jni.so 0x4656e988
D/08:31:54.999 Trying to load lib /data/data/com.netflix.mediaclient/lib/libnetflixmp_jni.so 0x4656e988
D/08:31:54.999 htcFlashPlugin::htcFlashPlugin
D/08:31:54.939 GC_EXTERNAL_ALLOC freed 291 objects / 17992 bytes in 26ms
D/08:31:54.909 GC_EXTERNAL_ALLOC freed 1296 objects / 92008 bytes in 29ms
well now it works....
With Android Market, I updated Adobe Flash to 10.3 (as well as Youtube and Google Maps updates), and now it works. Right before that I also resynced everything (but that didn't do diddly).
So I don't know if the Adobe Flash update fixed it. I could try removing the update and re-running Netflix - but that's what *seems* to be my case at first glance.
My girlfriend's Evo is doing the very same thing - and hers is stock and unrooted (brand new, just purchased yesterday) - so when she gets home tonight, I'll try the same thing - update to Flash 10.3, and see if her Netflix then runs correctly. I'll follow up with results here afterwards.
Wifflepig said:
Attached is a ZIP that has logfiles for just netflix activity from starting it up to closing it out, as well as another file that has all entries during that same time period. Also, here's the logs surrounding Netflix:
Code:
Process Monitor Widget (logcat)
===============================
Process Netflix(com.netflix.mediaclient)
D/08:32:22.469 GC_EXPLICIT freed 89 objects / 4456 bytes in 78ms
D/08:32:22.139 GC_EXPLICIT freed 1826 objects / 358504 bytes in 104ms
D/08:32:17.269 GC_FOR_MALLOC freed 9684 objects / 414472 bytes in 35ms
D/08:32:11.769 GC_FOR_MALLOC freed 4151 objects / 506824 bytes in 46ms
D/08:32:06.029 GC_FOR_MALLOC freed 5213 objects / 342464 bytes in 32ms
D/08:32:00.429 GC_FOR_MALLOC freed 33 objects / 1352 bytes in 95ms
D/08:31:57.809 GC_EXPLICIT freed 431 objects / 24816 bytes in 30ms
D/08:31:57.659 GC_EXPLICIT freed 2834 objects / 194272 bytes in 42ms
D/08:31:55.179 queueRequest with mProxyHost=null for https://uiboot.netflix.com/apps/mobileui/upgrade_policy?v=2.0&e=NFANDROID1-HTC==PC36100S-E9616F100D03D7657E858E038D039C3ACEEB08871A7088736019A9013578DFF1&device_type=NFANDROID1-&certification_version=1.2.0%20build%20819145-1.2.0-102
D/08:31:55.179 setProxyConfig mProxyHost=null
D/08:31:55.179 queueRequest to set proxy
D/08:31:55.179 [JWebCoreJavaBridge::resume] >> do resume
D/08:31:55.159 GC_FOR_MALLOC freed 2666 objects / 342392 bytes in 30ms
D/08:31:55.069 Settings::setMixedPluginEnabled 1
D/08:31:55.069 Settings::setMixedPluginEnabled 1
D/08:31:55.069 Settings::setMixedPluginEnabled 1
D/08:31:55.059 Settings::setMixedPluginEnabled 1
I/08:31:55.049 PluginManager::getPluginDirectories target:/data/data/com.adobe.flashplayer/lib
I/08:31:55.049 PluginManager::getPluginDirectories add:/system/lib/
I/08:31:55.039 PluginManager::getPluginDirectories target:/data/data/com.htc.flashliteplugin/lib
E/08:31:55.039 CheckOMX drm.play is not available done
E/08:31:55.039 CheckOMX drm.play is not available
I/08:31:55.039 listNode return 38
I/08:31:55.029 OMX interface is valid
I/08:31:55.029 Got IMediaPlayerService interface
I/08:31:55.029 Got IBinder interface to media.player
I/08:31:55.029 PluginManager::getPluginDirectories
I/08:31:55.009 Got IServiceManager interface
D/08:31:55.009 Shared lib '/data/data/com.netflix.mediaclient/lib/libnetflixmp_jni.so' already loaded in same CL 0x4656e988
D/08:31:55.009 Trying to load lib /data/data/com.netflix.mediaclient/lib/libnetflixmp_jni.so 0x4656e988
D/08:31:55.009 Added shared lib /data/data/com.netflix.mediaclient/lib/libnetflixmp_jni.so 0x4656e988
D/08:31:54.999 Trying to load lib /data/data/com.netflix.mediaclient/lib/libnetflixmp_jni.so 0x4656e988
D/08:31:54.999 htcFlashPlugin::htcFlashPlugin
D/08:31:54.939 GC_EXTERNAL_ALLOC freed 291 objects / 17992 bytes in 26ms
D/08:31:54.909 GC_EXTERNAL_ALLOC freed 1296 objects / 92008 bytes in 29ms
Click to expand...
Click to collapse
Just want to verify..
Are you getting the "device not supported" error?
Or are you getting a black screen?
Or does it work?
Sent from my HERO200 using XDA App
unCoRrUpTeD said:
Just want to verify..
Are you getting the "device not supported" error?
Or are you getting a black screen?
Or does it work?
Sent from my HERO200 using XDA App
Click to expand...
Click to collapse
Nope, I was getting the red Netflix logo, then a white screen and a message saying I should make sure my date and time was correct, then it'd exit (I'm the OP).
What fixed it for me was strange - I updated my Adobe Flash to 10.3 (as well as Google Maps and Youtube updates) and then it worked. Mine was a custom ROM (Azrael 4.0).
My GFs Evo 4G - had the very same issue - and hers is stock, unrooted - brand new. I tried updating her Flash to 10.3, also did a update to her Maps and Youtube - and it *didn't* fix it. That is, until she rebooted her phone, and let it sit for about 10 minutes and tried once more - then it worked.
It seems really odd that there'd be a wait time that would make it work - maybe it's something network related (with their network), or just a crap shoot. Dunno, but we're both working now.
Anyone who can actually get it to work (getting it to work defined as actually streaming audio and/or video without crashing ever) able to post their logcat file right before and during the first few seconds of streaming?
Would prefer logs from htc devices since that's what I have, but any would be appreciated.
I'd just like to compare it to the logcats showing errors. If audio/video quality is not perfect on your device for netflix, please note that so it can be factored in.
I found a reference to drm.play in /system/lib/libstagefrighthw.so compiled library for some of the htc sense 2.3 roms. Not sure how relevant it is at the moment since it's just a error message string.
@mem addr: 00003180h
drm.play.error: StagefrightSurfaceOutput7x30::createRenderer returning NULL!
Wifflepig said:
Nope, I was getting the red Netflix logo, then a white screen and a message saying I should make sure my date and time was correct, then it'd exit (I'm the OP).
What fixed it for me was strange - I updated my Adobe Flash to 10.3 (as well as Google Maps and Youtube updates) and then it worked. Mine was a custom ROM (Azrael 4.0).
My GFs Evo 4G - had the very same issue - and hers is stock, unrooted - brand new. I tried updating her Flash to 10.3, also did a update to her Maps and Youtube - and it *didn't* fix it. That is, until she rebooted her phone, and let it sit for about 10 minutes and tried once more - then it worked.
It seems really odd that there'd be a wait time that would make it work - maybe it's something network related (with their network), or just a crap shoot. Dunno, but we're both working now.
Click to expand...
Click to collapse
I remember that now (and thats what the title says). Jumping through different threads starts getting me confused. I'm not able to use flash 10.3 or 10.2 on my phone, so hopefully I can work around that. Could you post another logcat now that it is working?
Have flash 10.3, Netflix starts, I select a movie and play it. It switches to the red load screen, then flickers and goes back to the Netflix home menu screen....won't play the video....
Jeremy
Evo 4g, unrevoked 3.2, fresh evo 4.0.0.4
I had this problem on my Asus TF300T tablet running Android 4.2.1. After clearing the data, removing all updates for the Netflix app and updating again, the issue was still there. It turns out that Netflix is very finicky about the network you're connected to. Mine has two routers: one for the wired devices and one for the wireless devices. The gateway is on the wired router and the wireless router goes out through it. Some posts advice to run a WAN test on the router and that's when I realized that the internal tools in the wireless router do not have access to the internet, although every wireless device connected to it has internet access, including my tablet in question. I switched the operation mode on the wireless router from router to access point. That fixed the Netflix sign in problem for me.
If you find that nothing works for you at home, try connecting somewhere else. If you have specific DNS servers in your (Android) network setup try without them.
Ronnie Barabas
Hi,
I was seeing lot of problems there with my G3 i never saw before. Firstly, Browser.apk was fine on my XXJPS. No FC. No reboots. Then, for some stupid reason i don't know my browser started crashing on sites like forum.xda-developers.com - or any other site with lot of stuff on it, when it was almost finishing loading. It doesn't even show FC. just closed and android was fine again after it closes.
Then, i thought it was only caused by Firmware, so i flashed to XXJPQ. Again the same thing, that has never happened to me on even that firmware.
I tried lots of custom roms, like Kyrillos' ROM 9.5, CyanogenMOD 7 a8 and on every android OS with EVERY alternative browser i tried, (Opera Mini, Dolphin,...) they get closed. No matter its stock or not, they got closed. Now, on Purumod Special Edition v2.0 it even forces ANDROID to reboot itself by opening the same huge page.
I checked logcat and opened xda-developers forum again with G3, and i figured those things.
===================================
V/browser ( 5315): BrowserActivity.onStart: [email protected]
V/browser ( 5315): BrowserActivity.onResume: [email protected]
V/browser ( 5315): BrowserActivity.onPageStarted: url = http://forum.xda-developers.com/
V/browser ( 5315): onReceive : info.isAvailable() - true
V/browser ( 5315): BrowserActivity.onPageStarted: url = http://forum.xda-developers.com/setcompact.php?true
V/browser ( 5315): BrowserActivity.shouldOverrideUrlLoading: url = http://forum.xda-developers.com/setcompact.php?true webview = [email protected]
V/browser ( 5315): BrowserActivity.onPageStarted: url = http://forum.xda-developers.com/
V/browser ( 5315): BrowserActivity.shouldOverrideUrlLoading: url = http://forum.xda-developers.com/ webview = [email protected]
W/PowerManagerService( 4908): Timer 0x3->0x3|0x0
--------- beginning of /dev/log/system
I/ActivityManager( 4908): Process com.sec.android.providers.downloads (pid 5168) has died.
I/ActivityManager( 4908): Process com.google.android.apps.uploader (pid 5296) has died.
I/ActivityManager( 4908): Low Memory: No more background processes.
I/ActivityManager( 4908): Process android.process.acore (pid 5036) has died.
W/ActivityManager( 4908): Scheduling restart of crashed service com.android.providers.contacts/.ContactsStartupService in 5000ms
I/ActivityManager( 4908): Low Memory: No more background processes.
I/ActivityManager( 4908): Process com.google.process.gapps (pid 5023) has died.
W/ActivityManager( 4908): Scheduling restart of crashed service com.google.android.gsf/.gtalkservice.service.GTalkService in 14666ms
I/ActivityManager( 4908): Low Memory: No more background processes.
I/ActivityManager( 4908): Process com.siine.ime:Capptain (pid 5351) has died.
W/ActivityManager( 4908): Scheduling restart of crashed service com.siine.ime/com.ubikod.capptain.android.service.CapptainService in 24323ms
I/ActivityManager( 4908): Low Memory: No more background processes.
I/ActivityManager( 4908): Process com.sec.android.app.sns (pid 5199) has died.
W/ActivityManager( 4908): Scheduling restart of crashed service com.sec.android.app.sns/.SnsService in 249930ms
I/ActivityManager( 4908): Low Memory: No more background processes.
D/WifiService( 4908): releaseWifiLockLocked: WifiLock{capptain-service type=1 [email protected]}
I/ActivityManager( 4908): Process com.sec.android.providers.drm (pid 5192) has died.
W/ActivityManager( 4908): Scheduling restart of crashed service com.sec.android.providers.drm/.OmaDrmConfigService in 33655ms
I/ActivityManager( 4908): Low Memory: No more background processes.
I/ActivityManager( 4908): Process com.sec.android.provider.logsprovider (pid 5062) has died.
I/ActivityManager( 4908): Low Memory: No more background processes.
E/installd( 2537): eof
E/installd( 2537): failed to read size
I/installd( 2537): closing connection
I/ServiceManager( 2522): service 'telephony.registry' died
I/ServiceManager( 2522): service 'batteryinfo' died
I/ServiceManager( 2522): service 'usagestats' died
I/ServiceManager( 2522): service 'meminfo' died
I/ServiceManager( 2522): service 'cpuinfo' died
I/ServiceManager( 2522): service 'permission' died
I/ServiceManager( 2522): service 'wifi' died
=========================================
and so on.. service 'blablabla...' died... then it reboots the system.
i also thing that may be caused by JavaScript. Without it it doesnt close.
But i dont wanna see pages without javascript. Some pages are buggy without it.
Any solutions?
I have the same problem too. even with dolphin brower it FC and reboot system. And i have an other problem with the stock android browser : when I try to log in somewhere the secure connection is needed Browser force close and I don(t know why. some help is welcome
same problem already discussed here:
http://forum.xda-developers.com/showthread.php?t=1536521
Problem is not there on stock eclair 2.1, also no memory drain there that leads to the crash. I had crashes on both kyrillos 9.5 and stock JPU/JPQ and JPS, so I assume it's an OS thing, and certainly not a custom rom issue.
Maybe android 2.2 's OS itself or browser support specific webpage features that cause this crash (flash?)
XDA page loads normal on eclair 2.1
p.s. still impressed by the speed of eclair, when you have some spare time....re-try it
Br.
Michel
vleutmans said:
Problem is not there on stock eclair 2.1, also no memory drain there that leads to the crash. I had crashes on both kyrillos 9.5 and stock JPU/JPQ and JPS, so I assume it's an OS thing, and certainly not a custom rom issue.
Maybe android 2.2 's OS itself or browser support specific webpage features that cause this crash (flash?)
XDA page loads normal on eclair 2.1
p.s. still impressed by the speed of eclair, when you have some spare time....re-try it
Br.
Michel
Click to expand...
Click to collapse
Which eclair rom ?
Sent from my GT-I5800 using Tapatalk 2 Beta-5
I5800XXJK1 the latest...and greatest I hope.
I just rooted this rom (superoneclick), then disabled some bloatware and for the rest didn't touch it.
despite eclair not being able to be a wifi hotspot by default,it still can be with separate software. So feature wise I don't miss anything at the moment.
If you want to have app2sd/hybrid data2sd on eclair without the usual delays, you can even install link2sd from market, and happily install lots of software with no lag.
Br.
Michel
if this issue is staying despite the change in roms then its one of two things... either its a problem deeply buried in your system and in which case PM hillbeast and ask him very nicely as im sure he has a zip file that can completely wipe your phone.
or its hardware... does your phone get very hot?
Ava.tar said:
if this issue is staying despite the change in roms then its one of two things... either its a problem deeply buried in your system and in which case PM hillbeast and ask him very nicely as im sure he has a zip file that can completely wipe your phone.
or its hardware... does your phone get very hot?
Click to expand...
Click to collapse
I think it's a problem in android 2.2 Froyo itself, so the OS.
I'm not underestimating the developers on Froyo, but I think they cannot solve OS malfunctions as they are used to focus on customizing only (feature and GUI wise).
Eclair is just a better platform for the i5800 hardware...to my humble opinion
Even the youtube audio/video out-of-sync is almost not present in eclair...imagine.
it reboots the phone?? dude, if dolphin and other browser force close, then i'm sure it's not the software problem.......
When I checked on froyo, then just before browser FC, I say a memory peak just before.
So when you open de xda page and monitor the memory usage of browser, then it goes from example 25 to 150 mb in a few seconds, then browser FC.
I will try purumod soon if I have some playing-time to check and combine it with link2sd, because app2sd always seems to cause lags and link2sd is fast.
guys i've no such issues over here& if someone is looking for zerofill.tar like avatar suggested above...you can find it in my mediafire...
btw: i can fully load xda page in following browsers: Maxthon, Operamini, Operamini next, Boat browser...idk for stock browser as i don't use it coz it's so slowww
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Sent from Galaxy
Hercolubus Rom v 2.0
powered by
G3mod by Arakmar 12/04/2012.zip
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
You can do this...
Flash your phone with zerofill.tar..
Then remove the partition from sd card using minitool and repartition using kernel used in cm7alpha8....
Just give it a try.
I used to get this problem once.not anymore.
Sent from my GT-I5800 using Tapatalk
prohank said:
You can do this...
Flash your phone with zerofill.tar..
Then remove the partition from sd card using minitool and repartition using kernel used in cm7alpha8....
Just give it a try.
I used to get this problem once.not anymore.
Sent from my GT-I5800 using Tapatalk
Click to expand...
Click to collapse
i recommend partitioning sdcard with minitool on a comp...coz if partitioned through cwm it could result a mass storage failure later on...it happened to me...and i always use minitool since then
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Sent from Galaxy
Hercolubus Rom v 2.0
powered by
G3mod by Arakmar 12/04/2012.zip
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
rkoby13 said:
i recommend partitioning sdcard with minitool on a comp...coz if partitioned through cwm it could result a mass storage failure later on...it happened to me...and i always use minitool since then
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Sent from Galaxy
Hercolubus Rom v 2.0
powered by
G3mod by Arakmar 12/04/2012.zip
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Click to expand...
Click to collapse
Weird! I always partition through cwm.never had a problem..
When did u try this?..it must have been an old cwm
Sent from my GT-I5800 using Tapatalk
prohank said:
Weird! I always partition through cwm.never had a problem..
When did u try this?..it must have been an old cwm
Sent from my GT-I5800 using Tapatalk
Click to expand...
Click to collapse
rkoby13 said:
i recommend partitioning sdcard with minitool on a comp...coz if partitioned through cwm it could result a mass storage failure later on...it happened to me...and i always use minitool since then
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Sent from Galaxy
Hercolubus Rom v 2.0
powered by
G3mod by Arakmar 12/04/2012.zip
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Click to expand...
Click to collapse
Yep, it happened the same to me as rkoby13 explained. Sounds weird/strange, prohank,
i know. But it is true.
You better use minitool as rkoby already said to avoid failures later on.
Just search for google to find it - it's free (type: MiniTool Partition Wizard)
regards
Galaxy3User said:
Yep, it happened the same to me as rkoby13 explained. Sounds weird/strange, prohank,
i know. But it is true.
You better use minitool as rkoby already said to avoid failures later on.
Just search for google to find it - it's free (type: MiniTool Partition Wizard)
regards
Click to expand...
Click to collapse
Any problems mate?
I said i never got such a problem still.does that mean i said "don't use minitool"?
i think i did not.:sly:
so i asked if it still happens in new cwm's as well? If it does then i wouldn't do it anymore.
And if you haven't heard of partitioning through cwm.
May be you should open google web page which is www.google.com and type "partitioning through cwm?" And then enter key.
And as for minitool thing i already use it.thx for the description.
So keep your kind info with yourself if you aren't asked.
I respect rkoby.he has helped me a llot of times.i don't think he will take this in a negative way
Cheers
Sent from my GT-I5800 using Tapatalk
Has anyone had this issue? After a while my maps will start and gmail will flip out and then show a black screen. They seem to always do it at the same time and will not start working again until a reboot. I have tried killing maps and gmail and letting them restart but it doesn't fix it.
Any ideas? Other things sometimes become unstable as well like the settings interface.
I have the same problem with Google Chrome (displaying white page only) but after killing it, everything is back to normal. For Gmail, most of the time a reboot is needed to fixh the issue on mine.
Same issue here. Calendar involved, too!
I noticed that when these apps crash (and also some games do too or refuse to start) the logs spit out a lot of this:
Code:
D/19:06:36.010 ShaderProgram(32720)
couldn't load the vertex shader!
D/19:06:36.010 ShaderProgram(32720)
couldn't load the vertex shader!
E/19:06:35.990 OpenGLRenderer(32720)
OpenGLRenderer is out of memory!
D/19:06:35.990 OpenGLRenderer(32720)
GL error from OpenGLRenderer: 0x505
D/19:06:35.980 NvOsDebugPrintf(32720)
NvRmChannelSubmit failed (err = 196623, SyncPointValue = 6897307)
E/19:06:35.980 OpenGLRenderer(32720)
OpenGLRenderer is out of memory!
D/19:06:35.980 OpenGLRenderer(32720)
GL error from OpenGLRenderer: 0x505
E/19:06:35.980 OpenGLRenderer(32720)
OpenGLRenderer is out of memory!
D/19:06:35.980 OpenGLRenderer(32720)
GL error from OpenGLRenderer: 0x505
D/19:06:35.970 NvOsDebugPrintf(32720)
NvRmChannelSubmit failed (err = 196623, SyncPointValue = 6897307)
E/19:06:35.970 OpenGLRenderer(32720)
OpenGLRenderer is out of memory!
D/19:06:35.970 OpenGLRenderer(32720)
GL error from OpenGLRenderer: 0x505
E/19:06:35.970 OpenGLRenderer(32720)
OpenGLRenderer is out of memory!
Is this a software problem or a hardware issue with my tablet?
I'll have to flash another rom and see if this still happens.
Hi guys.
I had the same problem with my A510. Restarting gmail didn't work. So I did hard reset and all the problems are gone now.
I think I discovered the cause for this on my tablet. I was using the live wallpaper Galaxy Pack. I stopped using this live wallpaper a few days ago and have not had this error since.