Hello everyone!
I recently started having some rather strange issuses with my phone . This started about 2 weeks ago if I can recall .
First of all , you can find my entire setup in the signature .
Secondly , this happenned about 2 days before I flashed TheWhisp's TWRP . Before that I had my ordinary setup that I've been using for like 6 months .
Now , the first problem I ran into is that the phone seems to freeze for no reason out of the blue . I just left it locked , and when I tried to unlock it some hours later , the status bar was gone , the lockscreen could be interacted with and unlocked , but the launcher and all the interface was frozen . I could bring up the recent apps view by holding down the Home button , so I tried opening Samsung's task manager , but after tapping on the button , the phone was still frozen and no task manager was shown .
A wierd thing about this is that I'd been getting crashes for like every 6h 2 weeks ago , but starting 1 week ago , I've been getting them for like every 12h or sometimes even more .
I've tried fixing this in all the ways I can think of - re-flashed Peter's ROM , re-flashed back all the way from stock , changed the recovery back to CWM 5 , none seem to have worked unfortunately .
Another problem I've noticed recently (starting about 2 days ago) is that the battery is draining a lot faster as well . With a setup and usage that a month ago could keep it up for at least 24h , now it barely resists 18h with a less intense usage .
And finally , here's where the "anyone else ?" title part comes in : it may sound crazy , but I have a friend who's also got a Mini 2 , but unlike mine , his is full stock (no root , no custom recovery , he left it right as he bought it) . And the crazy part is that he's having problems with his phone as well! At the same time as I do! We were attending a class last week and my phone got a crash , then I had this random idea that maybe his phone will crash at the same time , since he told me he's been getting crashes too , so I told him to check his phone and voila ! He got one too . The difference between our phones is that he actually gets reboots , whereas my phone freezes completely and doesn't self reboot .
And now for some actually helpful info , here's something that keeps popping up continuously on the logcat , regardless of what I'm doing with the phone - haven't seen this before in none of my logcats before this problem came up :
Code:
D/PowerManagerService( 198): acquireWakeLock flags=0x1 tag=AlarmManager
D/PowerManagerService( 198): releaseWakeLock flags=0x1 tag=AlarmManager
E/AlarmManagerService( 198): android_server_AlarmManagerService_set to type=2,
1392.681000000
D/PowerManagerService( 198): acquireWakeLock flags=0x1 tag=AlarmManager
D/PowerManagerService( 198): releaseWakeLock flags=0x1 tag=AlarmManager
E/AlarmManagerService( 198): android_server_AlarmManagerService_set to type=2,
1392.781000000
D/PowerManagerService( 198): acquireWakeLock flags=0x1 tag=AlarmManager
D/PowerManagerService( 198): releaseWakeLock flags=0x1 tag=AlarmManager
E/AlarmManagerService( 198): android_server_AlarmManagerService_set to type=2,
1392.881000000
D/PowerManagerService( 198): acquireWakeLock flags=0x1 tag=AlarmManager
D/PowerManagerService( 198): releaseWakeLock flags=0x1 tag=AlarmManager
E/AlarmManagerService( 198): android_server_AlarmManagerService_set to type=2,
1392.981000000
D/PowerManagerService( 198): acquireWakeLock flags=0x1 tag=AlarmManager
D/PowerManagerService( 198): releaseWakeLock flags=0x1 tag=AlarmManager
E/AlarmManagerService( 198): android_server_AlarmManagerService_set to type=2,
1393.081000000
D/PowerManagerService( 198): acquireWakeLock flags=0x1 tag=AlarmManager
D/PowerManagerService( 198): releaseWakeLock flags=0x1 tag=AlarmManager
I would be very grateful if someone could help me! I'll have to go on a 2-day trip next week and I don't want the phone to die on me when I need it the most xD
Thanks alot guys and have a nice day!
Does this happen on all ROMs ? (including stock and CM)
Wake lock is responsible for when your device is or is not sleeping. For example, when all apps haven't released wake lock, the device won't go into deep sleep. For now, the best you can do is to revert back to everything stock. Don't log in your Google account or any other account, disable sync, leave it completely stock and see if the problem persist. It seems that something is acquiring wake lock on your device. A virus perhaps? It may sound crazy, but it could be due to some files on your sd and/or infected accounts and so on.. Wipe everything, even both storages
I've just flashed back completely to stock , without wiping the internal & external memory , didn't even connect to my Google account , and looks like the alarmManager lines don't appear anymore on the logcat .
I'm going to start re-installing (not restoring) my old stuff onto my phone and logcat after every major change (app install , kernel install etc) to see if and why the problem appears again .
Thanks for the help! It didn't occour to me that it may be a virus . I'm not an app whizz and don't install a lot of new stuff onto my phone , but unfortunately I don't remember whether I had installed anything fishy before this error started popping up .
I'll keep you updated if I manage to find its source .
Update :
Looks like I've managed to get rid of the alarmManager messages . They were caused by an app called AppLock .
HOWEVER that was not the problem . I've installed AppLock just some days ago . It could have been the faster battery drain cause , but not the crashes cause . My phone was frozen after a missed call (didn't have access to the PC so couldn't get a logcat) about 1h ago .
I've now noticed something else on the logcat - graphics related . I've attached an aLogcat ss (still away from my PC) .
One thing I forgot to mention is that video playback has been pretty grumpy . Every half an hour of playback or so , VPlayer would crash and no other player would work without a reboot .
Since no one else seems to have this problem, you could observe hardware failure.
Wipe batery
Wiping battery stats doesn't help. If you're running android 4+ you could try using Greenify (at least for battery drain)
I had this problem with my galaxy mini (not 2) found out I installed a dodgy app, once I uninstalled it problem was gone.
pryerlee said:
I had this problem with my galaxy mini (not 2) found out I installed a dodgy app, once I uninstalled it problem was gone.
Click to expand...
Click to collapse
You're right, sometime app create (for some reason, why?) zombie processes that uses a lot of battery
Okay so I'm still experiencing this problem with my phone . Hopefully this is not a hardware failure , as a full stock reset will fix it . So it is most likely some virus inside some app , which is wierd because I didn't install some dubious app at all . I have been using all these apps for quite some time and I can't seem to figure out which one might cause the problem . I'm thinking of Poweramp / Rocket Player / AppLock , which I've had some fun with lately , and my Poweramp trial expired , but it's been long since that .
Starting Monday , I will have the time to monitor the phone properly and look into the problem as I should have a long time ago . But until then , I want to check one more thing . I've caught this exception being thrown about every 5 seconds after the system had frozen . From the looks of it and from the research I've done , something might be trying to make a purchase (as I said , it might truly be a virus) but since I have no payment method registered with my Google account , it can't make that purchase , thus throwing an exception . Or maybe it over-flooded some service with requests , which crashed , taking some vital part in the Android workflow down with it , thus causing the freezes .
Here's the exception . If anyone knows whether it is related to some known virus , please let me know .
Code:
W/ActivityManager( 198): Failure sending broadcast Intent { act=android.intent.action.BATTERY_CHANGED flg=0x60000000 (has extras) }
W/ActivityManager( 198): android.os.DeadObjectException
W/ActivityManager( 198): at android.os.BinderProxy.transact(Native Method)
W/ActivityManager( 198): at android.app.ApplicationThreadProxy.scheduleRegisteredReceiver(ApplicationThreadNative.java:761)
W/ActivityManager( 198): at com.android.server.am.ActivityManagerService.performReceiveLocked(ActivityManagerService.java:10857)
W/ActivityManager( 198): at com.android.server.am.ActivityManagerService.deliverToRegisteredReceiverLocked(ActivityManagerService.java:10922)
W/ActivityManager( 198): at com.android.server.am.ActivityManagerService.processNextBroadcast(ActivityManagerService.java:10979)
W/ActivityManager( 198): at com.android.server.am.ActivityManagerService.access$100(ActivityManagerService.java:143)
W/ActivityManager( 198): at com.android.server.am.ActivityManagerService$2.handleMessage(ActivityManagerService.java:1082)
W/ActivityManager( 198): at android.os.Handler.dispatchMessage(Handler.java:99)
W/ActivityManager( 198): at android.os.Looper.loop(Looper.java:130)
W/ActivityManager( 198): at com.android.server.am.ActivityManagerService$AThread.run(ActivityManagerService.java:1337)
W/ActivityManager( 198): Unattached app died before broadcast acknowledged, skipping
Full wipe internal and external storage (i don't recommend you backup the data) install Stock ROM with stock recovery too not the cwm. And then don't install apps that are not popular or any app that you don't find in google play
Sent from my GT-S5570 using xda app-developers app
just go back to stock that what i did and that's ut everything working fine ^^
Related
Running CM 5071
For some reason YouTube doesn't seem to work right.
Sometimes it freezes and force closes when I try and play a video... and if it DOES load up without a freeze/force close I will hear the audio just fine but the picture will stay frozen. It just wont move, If I skip ahead it will show that frame, the audio will still keep going but the picture will still remain frozen... what could I possibly try to fix this?
Any ideas on this?
Same problem.
One of 2 things happens:
1. video plays but is stuck on the first frame, sound continues
seeking in the video will change the frame it is stuck on
2. you get an error: 'sorry, this video cannot be played'
Hitting 'ok' here will actually cause a force close, or the phone will become so lethargic that a battery pull is necessary
3. you are greeted with a black screen and the only response from the phone is the haptic feedback on the back/menu/home/search buttons.
The buttons are illuminated, screen is not.
This was happening with Froyo, and now CM 5.0.7
I went back to CM because of this problem, and it seems to have persisted.
Someone has GOT to know something....
Thank you. You have described our problem so much better than me, hopefully someone knows of a fix.
I'm guessing this has something to do with FroYo.
Before you upgraded to FroYo, did you at any point install the "Always HQ" YouTube hack? I was wondering if that had anything to do with that, maybe pushing the original YouTube APK will fix it.
lance713 said:
Thank you. You have described our problem so much better than me, hopefully someone knows of a fix.
I'm guessing this has something to do with FroYo.
Before you upgraded to FroYo, did you at any point install the "Always HQ" YouTube hack? I was wondering if that had anything to do with that, maybe pushing the original YouTube APK will fix it.
Click to expand...
Click to collapse
No.. but my limited knowledge of java is not helping me.
I am trying to figure out what is going wrong... there is a lot of 'not so nice looking' stuff in the logs.
What I have tried:
CM 5.0.6, CM 5.0.7
Wipes of davlik, cache, data, etc.
fix_permissions
'Fix apk UID mismatch' in recovery
Nothing has changed.
Stuff worthy of noting.. there are a LOT of these interesting lines in the logs:
05-27 06:50:45.408 W/ResourceType( 113): Resources don't contain package for resource number 0x7f050000
05-27 06:50:45.408 W/ResourceType( 113): Resources don't contain package for resource number 0x7f020005
The 'resource number' at the end is often repeated and there are about 30 or so lines.
I suspect the froyo update has left something behind that has to go away...
Still looking
do me a favor, use skyfire and try to watch a video. For me it always gets stuck on 25%, I wonder if it's related.
Edit: seems like this is also a problem with videos loaded on the sd. Tried watching a tv show I downloaded. Black screen, lights lit, force close.
video I recorded.. Full audio, frame freezes. Seek freezes a new frame.
Camera in video mode is causing a hard crash on mine.
When I change to video mode the phone locks up for 10 seconds with no response and then reboots.
I am guessing that's the watchdog in the kernel kicking in and rebooting it.
Overall not a good sign.
I am " bumping" this post because I am experiencing the SAME THING EXACTLY!!!
I performed all the same steps as the previous posters.
I was on Froyo... and it happened then. Then I did a Nandroid restore back to CM 5.0.7 and still the same problem exists.
I cannot play ANY video files... Youtube, TV.com, camera recorded videos.
I do hear the audio.
This is so aggravating. Everything else is running fine. But for me this is a big issues.
Thanks for any input, help, or advice!
Found something in a Google search, but it was posted to the cyanogen forums, which have been down all day.
The Google cache of it does not have the information.
The topic has the title '[Solution] Nexus One Won't Play Any Videos after Froyo'
Looks like someone @ cyanogen figured it out but we can't get at the forum to see the fix.
Here is some more information from the logs:
05-27 14:43:13.597 W/QCvdec ( 99): get_parameter: unknown param 0ff7a347
05-27 14:43:13.697 W/QCvdec ( 99): H264_Utils::check_header
05-27 14:43:13.697 W/QCvdec ( 99): check_header: start code 26
05-27 14:43:13.707 W/QCvdec ( 99): H264_Utils::check_header
05-27 14:43:13.707 W/QCvdec ( 99): check_header: start code 8
05-27 14:43:13.707 W/QCvdec ( 99): vdec_open
05-27 14:43:13.707 E/QCvdec ( 99): adsp: cannot open '/dev/vdec', fd: -1 (Out of memory)
05-27 14:43:13.707 W/QCvdec ( 99): Adsp Open Failed
05-27 14:43:13.707 W/QCvdec ( 99): adsp_close: adsp_module is not initialized
05-27 14:43:13.707 W/QCvdec ( 99): FA: Setting Tail to NULL
05-27 14:43:13.707 W/QCvdec ( 99): ERROR!!! vdec_open failed
05-27 14:43:13.707 W/QCvdec ( 99): Native decoder creation failed
05-27 14:43:13.707 W/QCvdec ( 99): ETB in Invalid State
Click to expand...
Click to collapse
I am showing plenty of free memory so I wonder if that device actually exists (/dev/vdec)
I can't get the file explorer running in DDMS for some reason... and I just don't know squat about this kind of debugger.
I am a gdb fan myself
But I keep poking around......
Solution found!
It's the radio!
Get the older radio from here:
http://forum.xda-developers.com/showpost.php?p=6026480&postcount=3
Call me crazy... but it works now.
I flashed:
32.26.00.24U_4.04.00.03_2 download MD5: c55116d119e9e30cffc86875dce1a560
camera works, phone works, youtube works....
Also I am on T-Mo.. no idea if this makes a difference but just in case.
videos work again after flashing the old radio! Thank you for finding the fix.
this is not just froyo, because this happened to me 2 weeks ago and my youtube app STILL does not work. i am still on 2.1 and there are other posts about this exact issue, but no fix has ever been found. i think it just is something on googles end, cause i did not do anything and suddenly my youtube started doing this. the video freezes but the audio continues.
RogerPodacter said:
this is not just froyo, because this happened to me 2 weeks ago and my youtube app STILL does not work. i am still on 2.1 and there are other posts about this exact issue, but no fix has ever been found. i think it just is something on googles end, cause i did not do anything and suddenly my youtube started doing this. the video freezes but the audio continues.
Click to expand...
Click to collapse
All of the symptoms I had seemed related to video.
Youtube did not work, recording video caused the phone to reboot, and so forth.
Does your camera record video?
One thing I noted only hours after I installed froyo over CM was that some streaming apps force closed..
Then the next day I noticed the youtube problem.
Then today is when I noticed the camera problem because I don't shoot video with the phone and the still camera still functioned normally.
I was running stock, then I went to CM, then to froyo and back again.
What is stumping me is what the radio had to do with this?
I don't know enough about the internals to come up with that.
Sorry I wish I had more for you
Nope I can still record video just fine. No reboots here. It's only with the YouTube app which doesn't work anymore.
Have the same problem.
CM to FROYO, with new RADIO, back to 5.0.7 and Youtube or camera viedo does not work.
Will try downgrade RADIO image.
will use this one:
32.26.00.24U_4.04.00.03_2
I can also confirm that downgrading the radio allows the youtube videos to work again. Whew!
Maybe that's why the official froyo release is taking so long -- because the new radio trashes youtube?
Sorry if this has been posted before but I cannot find it anywhere on this forum.
When I unlock my phone, there is a good 1-2 seconds before the lockscreen appears, whereas a few days ago it used to be instant.. not installed any dodgy apps in the mean time (that I can see anyway)
Anyone else had the same issue?
What ROM are you running?
It was almost instant with stock android 2.1 and 2.2... now it's instant with darky's rom. try hard reset or another lock screen app.
I am running Darky's 7.7 also.. just done a factory reset and tried a stock rom but still the same.. Might be something to do with hardware now me thinks!
There should be a delay. 2 seconds doesn't sound normal, but it shouldn't be instant either.
Delay = phone in deep sleep = saving battery.
No delay = phone not sleeping = draining battery
It seems like the app either hangs at the login loading indicator or just quit prematurely. Is there any fix for this yet?
Well, I decided to dig around logcat to see what the issue was:
Got this when it hung at the loading indicator:
Code:
D/skype ( 2081): Transport.connect fails. Sleeping for a second.
D/skype ( 2081): Transport.connect fails. Sleeping for a second.
V/SID ( 2081): AVTransportWrapper (/tmp/pcm_from_skypekit_key): connected!
V/SID ( 2081): AVTransportWrapper (/tmp/pcm_to_skypekit_key): connected!
And then after canceling, got this:
Code:
I/dalvikvm( 2081): Uncaught exception thrown by finalizer (will be discarded):
I/dalvikvm( 2081): Ljava/lang/NullPointerException;:
I/dalvikvm( 2081): at com.skype.ipc.SkypeKitRunner.stopApp((null):-1)
I/dalvikvm( 2081): at com.skype.ipc.SkypeKitRunner.finalize((null):-1)
I/dalvikvm( 2081): at dalvik.system.NativeStart.run(Native Method)
V/SID ( 2081): UnixSocket.cpp:269(bool Sid::UnixSocket::Poll(int, short int, int)): poll error: m_Key: /tmp/pcm_from
_skypekit_key, revents: 0x11
V/SID ( 2081): SocketTransport.cpp:143(int Sid::SocketTransport::ReadToBuf(char*, int, int)): Poll error: 11
V/SID ( 2081): SidAVServer.cpp:90(Sid::Protocol::Status Sid::AVServer::ProcessCommands()): AVServerSession::ProcessCommands command reading failed: 1
V/SID ( 2081): ~AVTransportWrapper exit
W/MessageQueue( 2081): null sending message to a Handler on a dead thread
W/MessageQueue( 2081): java.lang.RuntimeException: null sending message to a Handler on a dead thread
W/MessageQueue( 2081): at android.os.MessageQueue.enqueueMessage(MessageQueue.java:179)
W/MessageQueue( 2081): at android.os.Looper.quit(Looper.java:173)
W/MessageQueue( 2081): at com.skype.raider.service.w.b(Unknown Source)
W/MessageQueue( 2081): at com.skype.raider.service.bf.v(Unknown Source)
W/MessageQueue( 2081): at com.skype.raider.service.SkypeServiceController.onDestroy(Unknown Source)
W/MessageQueue( 2081): at android.app.ActivityThread.handleStopService(ActivityThread.java:3076)
W/MessageQueue( 2081): at android.app.ActivityThread.access$3700(ActivityThread.java:125)
W/MessageQueue( 2081): at android.app.ActivityThread$H.handleMessage(ActivityThread.java:2099)
W/MessageQueue( 2081): at android.os.Handler.dispatchMessage(Handler.java:99)
W/MessageQueue( 2081): at android.os.Looper.loop(Looper.java:123)
W/MessageQueue( 2081): at android.app.ActivityThread.main(ActivityThread.java:4627)
W/MessageQueue( 2081): at java.lang.reflect.Method.invokeNative(Native Method)
W/MessageQueue( 2081): at java.lang.reflect.Method.invoke(Method.java:521)
W/MessageQueue( 2081): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:868)
W/MessageQueue( 2081): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:626)
W/MessageQueue( 2081): at dalvik.system.NativeStart.main(Native Method)
It actually did sign me in once, and I got this from logcat:
Code:
D/skype ( 2081): Transport.connect fails. Sleeping for a second.
D/dalvikvm( 1011): GC_EXTERNAL_ALLOC freed 22734 objects / 1099360 bytes in 149ms
V/SID ( 2081): AVTransportWrapper (/tmp/pcm_from_skypekit_key): connected!
V/SID ( 2081): AVTransportWrapper (/tmp/pcm_to_skypekit_key): connected!
D/WifiService( 1011): ACTION_BATTERY_CHANGED pluggedType: 0
D/dalvikvm( 1011): GC_FOR_MALLOC freed 7222 objects / 347752 bytes in 114ms
I/ActivityManager( 1011): Starting activity: Intent { cmp=com.skype.raider/.ui.startup.FeatureTourActivity (has extras)
}
D/dalvikvm( 2081): GC_FOR_MALLOC freed 7362 objects / 509032 bytes in 34ms
I/dalvikvm( 2081): Uncaught exception thrown by finalizer (will be discarded):
I/dalvikvm( 2081): Ljava/lang/NullPointerException;:
I/dalvikvm( 2081): at com.skype.ipc.SkypeKitRunner.stopApp((null):-1)
I/dalvikvm( 2081): at com.skype.ipc.SkypeKitRunner.finalize((null):-1)
I/dalvikvm( 2081): at dalvik.system.NativeStart.run(Native Method)
E/MediaPlayerService( 906): create BoardHWPlayer
E/OMXPlayer( 906): Creating new NVOMXPlayer: 0x2b048
E/OMXPlayer( 906): 0x2b048 setDataSource url=droid://32:512404:72508
E/OMXPlayer( 906): render thread(14766) started: 0x2b048
E/OMXPlayer( 906): prepareAsync: 0x2b048
E/OMXPlayer( 906): prepare 0x2b048
E/OMXPlayer( 906): 0x2b048 Creating player for: droid://32:512404:72508
E/OMXPlayer( 906): prepare done 0x2b048
E/OMXPlayer( 906): render - signal wait 0x2b048
E/OMXPlayer( 906): start 0x2b048
E/OMXPlayer( 906): render - signal rx'd 0x2b048
D/dalvikvm( 1380): GC_EXPLICIT freed 10 objects / 368 bytes in 81ms
D/dalvikvm( 2081): GC_EXTERNAL_ALLOC freed 2280 objects / 159232 bytes in 28ms
I/ActivityManager( 1011): Displayed activity com.skype.raider/.ui.startup.FeatureTourActivity: 851 ms (total 851 ms)
E/OMXPlayer( 906): playback complete: 0x2b048
E/OMXPlayer( 906): playback complete - wait for signal 0x2b048
E/OMXPlayer( 906): reset: 0x2b048
D/ ( 906): setting block activity: 1
D/ ( 906): setting block activity: 0
E/OMXPlayer( 906): reset done 0x2b048
E/OMXPlayer( 906): destructor: 0x2b048
E/OMXPlayer( 906): playback complete - signal rx'd 0x2b048
E/OMXPlayer( 906): Worker Thread Exit -
D/ ( 910): NVRM_DAEMON(461): client process closed connection
D/ ( 910): NVRM_DAEMON(461): client process closed connection
D/ ( 910): NVRM_DAEMON(461): client process closed connection
E/OMXPlayer( 906): reset done 0x2b048
E/OMXPlayer( 906): destructor: 0x2b048 done
But then it crashed after the screen where it asks me if I want to sync all my contacts, and I said yes.
Code:
W/ActivityManager( 1011): Timeout executing service: ServiceRecord{4a787050 com.skype.raider/.service.SyncProviderServic
e}
I/Process ( 1011): Sending signal. PID: 2081 SIG: 3
I/dalvikvm( 2081): threadid=3: reacting to signal 3
I/dalvikvm( 2081): Wrote stack traces to '/data/anr/traces.txt'
I/Process ( 1011): Sending signal. PID: 1011 SIG: 3
I/dalvikvm( 1011): threadid=3: reacting to signal 3
I/dalvikvm( 1011): Wrote stack traces to '/data/anr/traces.txt'
I/Process ( 1011): Sending signal. PID: 14982 SIG: 3
I/dalvikvm(14982): threadid=3: reacting to signal 3
I/dalvikvm(14982): Wrote stack traces to '/data/anr/traces.txt'
I/Process ( 1011): Sending signal. PID: 1379 SIG: 3
I/dalvikvm( 1379): threadid=3: reacting to signal 3
I/dalvikvm( 1379): Wrote stack traces to '/data/anr/traces.txt'
I/Process ( 1011): Sending signal. PID: 1380 SIG: 3
I/dalvikvm( 1380): threadid=3: reacting to signal 3
I/dalvikvm( 1380): Wrote stack traces to '/data/anr/traces.txt'
I/Process ( 1011): Sending signal. PID: 2052 SIG: 3
I/dalvikvm( 2052): threadid=3: reacting to signal 3
I/dalvikvm( 2052): Wrote stack traces to '/data/anr/traces.txt'
I/Process ( 1011): Sending signal. PID: 14932 SIG: 3
I/dalvikvm(14932): threadid=3: reacting to signal 3
I/dalvikvm(14932): Wrote stack traces to '/data/anr/traces.txt'
I/Process ( 1011): Sending signal. PID: 1455 SIG: 3
I/dalvikvm( 1455): threadid=3: reacting to signal 3
I/dalvikvm( 1455): Wrote stack traces to '/data/anr/traces.txt'
I/Process ( 1011): Sending signal. PID: 1503 SIG: 3
I/dalvikvm( 1503): threadid=3: reacting to signal 3
I/dalvikvm( 1503): Wrote stack traces to '/data/anr/traces.txt'
I/Process ( 1011): Sending signal. PID: 14918 SIG: 3
I/dalvikvm(14918): threadid=3: reacting to signal 3
I/dalvikvm(14918): Wrote stack traces to '/data/anr/traces.txt'
I/Process ( 1011): Sending signal. PID: 14890 SIG: 3
I/dalvikvm(14890): threadid=3: reacting to signal 3
I/dalvikvm(14890): Wrote stack traces to '/data/anr/traces.txt'
I/Process ( 1011): Sending signal. PID: 14907 SIG: 3
I/dalvikvm(14907): threadid=3: reacting to signal 3
I/dalvikvm(14907): Wrote stack traces to '/data/anr/traces.txt'
I/Process ( 1011): Sending signal. PID: 14847 SIG: 3
I/dalvikvm(14847): threadid=3: reacting to signal 3
I/dalvikvm(14847): Wrote stack traces to '/data/anr/traces.txt'
I/Process ( 1011): Sending signal. PID: 20292 SIG: 3
I/dalvikvm(20292): threadid=3: reacting to signal 3
I/dalvikvm(20292): Wrote stack traces to '/data/anr/traces.txt'
I/Process ( 1011): Sending signal. PID: 1875 SIG: 3
I/dalvikvm( 1875): threadid=3: reacting to signal 3
I/dalvikvm( 1875): Wrote stack traces to '/data/anr/traces.txt'
I/Process ( 1011): Sending signal. PID: 5481 SIG: 3
I/dalvikvm( 5481): threadid=3: reacting to signal 3
I/dalvikvm( 5481): Wrote stack traces to '/data/anr/traces.txt'
I/Process ( 1011): Sending signal. PID: 5426 SIG: 3
I/dalvikvm( 5426): threadid=3: reacting to signal 3
I/dalvikvm( 5426): Wrote stack traces to '/data/anr/traces.txt'
I/Process ( 1011): Sending signal. PID: 1388 SIG: 3
I/dalvikvm( 1388): threadid=3: reacting to signal 3
I/dalvikvm( 1388): Wrote stack traces to '/data/anr/traces.txt'
I/Process ( 1011): Sending signal. PID: 1922 SIG: 3
I/dalvikvm( 1922): threadid=3: reacting to signal 3
I/dalvikvm( 1922): Wrote stack traces to '/data/anr/traces.txt'
I/Process ( 1011): Sending signal. PID: 3150 SIG: 3
I/dalvikvm( 3150): threadid=3: reacting to signal 3
I/dalvikvm( 3150): Wrote stack traces to '/data/anr/traces.txt'
I/Process ( 1011): Sending signal. PID: 3031 SIG: 3
I/dalvikvm( 3031): threadid=3: reacting to signal 3
I/dalvikvm( 3031): Wrote stack traces to '/data/anr/traces.txt'
I/Process ( 1011): Sending signal. PID: 3024 SIG: 3
I/dalvikvm( 3024): threadid=3: reacting to signal 3
I/dalvikvm( 3024): Wrote stack traces to '/data/anr/traces.txt'
I/Process ( 1011): Sending signal. PID: 3009 SIG: 3
I/dalvikvm( 3009): threadid=3: reacting to signal 3
I/dalvikvm( 3009): Wrote stack traces to '/data/anr/traces.txt'
I/Process ( 1011): Sending signal. PID: 30776 SIG: 3
I/dalvikvm(30776): threadid=3: reacting to signal 3
I/dalvikvm(30776): Wrote stack traces to '/data/anr/traces.txt'
I/Process ( 1011): Sending signal. PID: 30031 SIG: 3
I/dalvikvm(30031): threadid=3: reacting to signal 3
I/dalvikvm(30031): Wrote stack traces to '/data/anr/traces.txt'
I/Process ( 1011): Sending signal. PID: 1514 SIG: 3
I/dalvikvm( 1514): threadid=3: reacting to signal 3
I/dalvikvm( 1514): Wrote stack traces to '/data/anr/traces.txt'
I/Process ( 1011): Sending signal. PID: 1965 SIG: 3
I/dalvikvm( 1965): threadid=3: reacting to signal 3
I/dalvikvm( 1965): Wrote stack traces to '/data/anr/traces.txt'
E/ActivityManager( 1011): ANR in com.skype.raider
E/ActivityManager( 1011): Reason: Executing service com.skype.raider/.service.SyncProviderService
E/ActivityManager( 1011): Load: 0.34 / 0.16 / 0.16
E/ActivityManager( 1011): CPU usage from 10344ms to 11ms ago:
E/ActivityManager( 1011): system_server: 2% = 1% user + 1% kernel / faults: 87 minor 2 major
E/ActivityManager( 1011): y.mobile:remote: 0% = 0% user + 0% kernel / faults: 3256 minor
E/ActivityManager( 1011): ogle.android.gm: 0% = 0% user + 0% kernel / faults: 65 minor
E/ActivityManager( 1011): events/0: 0% = 0% user + 0% kernel
E/ActivityManager( 1011): e.process.gapps: 0% = 0% user + 0% kernel / faults: 56 minor 1 major
E/ActivityManager( 1011): android.browser: 0% = 0% user + 0% kernel / faults: 50 minor 1 major
E/ActivityManager( 1011): mmcqd: 0% = 0% user + 0% kernel
E/ActivityManager( 1011): droid.wallpaper: 0% = 0% user + 0% kernel / faults: 22 minor
E/ActivityManager( 1011): ft.keyboardplus: 0% = 0% user + 0% kernel / faults: 16 minor
E/ActivityManager( 1011): om.skype.raider: 0% = 0% user + 0% kernel / faults: 33 minor
E/ActivityManager( 1011): com.svox.pico: 0% = 0% user + 0% kernel / faults: 24 minor
E/ActivityManager( 1011): nie.geniewidget: 0% = 0% user + 0% kernel / faults: 64 minor
E/ActivityManager( 1011): viders.calendar: 0% = 0% user + 0% kernel / faults: 23 minor
E/ActivityManager( 1011): TOTAL: 9% = 2% user + 2% kernel + 0% iowait + 4% softirq
D/skia ( 1011): purging 193K from font cache [25 entries]
Force closed Skype, restarted it, and got this:
Code:
I/ActivityManager( 1011): Starting activity: Intent { act=android.intent.action.MAIN cat=[android.intent.category.LAUNCH
ER] flg=0x10200000 cmp=com.skype.raider/.ui.SplashScreenActivity }
I/ActivityManager( 1011): Start proc com.skype.raider for activity com.skype.raider/.ui.SplashScreenActivity: pid=17662
uid=10057 gids={3003, 1015}
D/dalvikvm(17662): Debugger has detached; object registry had 1 entries
D/dalvikvm(17662): GC_FOR_MALLOC freed 2011 objects / 137984 bytes in 30ms
I/ActivityManager( 1011): Starting activity: Intent { cmp=com.skype.raider/.ui.startup.IntroToSkypeActivity (has extras)
}
I/ActivityManager( 1011): Starting activity: Intent { flg=0x4000000 cmp=com.skype.raider/.ui.startup.SignInActivity (has
extras) }
W/Resources(17662): Converting to string: TypedValue{t=0x12/d=0x0 a=2 r=0x7f0d0021}
W/Resources(17662): Converting to string: TypedValue{t=0x12/d=0x0 a=2 r=0x7f0d0021}
D/FlurryAgent(17662): Starting new session
D/FlurryAgent(17662): Sending report to: http://data.flurry.com/aar.do
I/Process (17662): Sending signal. PID: 14594 SIG: 9
I/Process (17662): Sending signal. PID: 14598 SIG: 9
I/Process (17662): Sending signal. PID: 14600 SIG: 9
I/Process (17662): Sending signal. PID: 14601 SIG: 9
I/Process (17662): Sending signal. PID: 14602 SIG: 9
I/Process (17662): Sending signal. PID: 14604 SIG: 9
I/Process (17662): Sending signal. PID: 14605 SIG: 9
I/Process (17662): Sending signal. PID: 14606 SIG: 9
I/Process (17662): Sending signal. PID: 14608 SIG: 9
I/Process (17662): Sending signal. PID: 14619 SIG: 9
I/Process (17662): Sending signal. PID: 14757 SIG: 9
I/global (17662): Default buffer size used in BufferedInputStream constructor. It would be better to be explicit if an
8k buffer is required.
D/dalvikvm(17662): GC_FOR_MALLOC freed 3538 objects / 234272 bytes in 36ms
D/skype (17662): Transport.connect fails. Sleeping for a second.
D/dalvikvm( 1011): GC_EXTERNAL_ALLOC freed 20621 objects / 1039464 bytes in 122ms
D/FlurryAgent(17662): Report successful
I/ActivityManager( 1011): Displayed activity com.skype.raider/.ui.startup.SignInActivity: 1014 ms (total 2835 ms)
D/dalvikvm(17662): Trying to load lib /data/data/com.skype.raider/lib/libpcmhost.so 0x4a59e608
D/dalvikvm(17662): Added shared lib /data/data/com.skype.raider/lib/libpcmhost.so 0x4a59e608
V/SID (17662): AVTransportWrapper (/tmp/pcm_from_skypekit_key): connected!
V/SID (17662): AVTransportWrapper (/tmp/pcm_to_skypekit_key): connected!
D/skia ( 1011): purging 196K from font cache [26 entries]
D/dalvikvm( 3024): GC_EXPLICIT freed 451 objects / 19984 bytes in 57ms
D/WifiService( 1011): ACTION_BATTERY_CHANGED pluggedType: 0
D/dalvikvm(14847): GC_EXPLICIT freed 5798 objects / 776232 bytes in 75ms
D/dalvikvm( 1455): GC_EXPLICIT freed 533 objects / 25688 bytes in 69ms
D/dalvikvm( 1388): GC_EXPLICIT freed 470 objects / 45040 bytes in 84ms
And got the following ANR trace that I sent to Skype. It's attached to this post.
Working fine for me on vegan 5.1
Which rom/kernel re you using? is this a vegan 5.1 problem? I am vegan 5.1.with clemsys latest
thomasca said:
Well, I decided to dig around logcat to see what the issue was:
Got this when it hung at the loading indicator:
Code:
D/skype ( 2081): Transport.connect fails. Sleeping for a second.
D/skype ( 2081): Transport.connect fails. Sleeping for a second.
V/SID ( 2081): AVTransportWrapper (/tmp/pcm_from_skypekit_key): connected!
V/SID ( 2081): AVTransportWrapper (/tmp/pcm_to_skypekit_key): connected!
And then after canceling, got this:
Code:
I/dalvikvm( 2081): Uncaught exception thrown by finalizer (will be discarded):
I/dalvikvm( 2081): Ljava/lang/NullPointerException;:
I/dalvikvm( 2081): at com.skype.ipc.SkypeKitRunner.stopApp((null):-1)
I/dalvikvm( 2081): at com.skype.ipc.SkypeKitRunner.finalize((null):-1)
I/dalvikvm( 2081): at dalvik.system.NativeStart.run(Native Method)
V/SID ( 2081): UnixSocket.cpp:269(bool Sid::UnixSocket::Poll(int, short int, int)): poll error: m_Key: /tmp/pcm_from
_skypekit_key, revents: 0x11
V/SID ( 2081): SocketTransport.cpp:143(int Sid::SocketTransport::ReadToBuf(char*, int, int)): Poll error: 11
V/SID ( 2081): SidAVServer.cpp:90(Sid::Protocol::Status Sid::AVServer::ProcessCommands()): AVServerSession::ProcessCommands command reading failed: 1
V/SID ( 2081): ~AVTransportWrapper exit
W/MessageQueue( 2081): null sending message to a Handler on a dead thread
W/MessageQueue( 2081): java.lang.RuntimeException: null sending message to a Handler on a dead thread
W/MessageQueue( 2081): at android.os.MessageQueue.enqueueMessage(MessageQueue.java:179)
W/MessageQueue( 2081): at android.os.Looper.quit(Looper.java:173)
W/MessageQueue( 2081): at com.skype.raider.service.w.b(Unknown Source)
W/MessageQueue( 2081): at com.skype.raider.service.bf.v(Unknown Source)
W/MessageQueue( 2081): at com.skype.raider.service.SkypeServiceController.onDestroy(Unknown Source)
W/MessageQueue( 2081): at android.app.ActivityThread.handleStopService(ActivityThread.java:3076)
W/MessageQueue( 2081): at android.app.ActivityThread.access$3700(ActivityThread.java:125)
W/MessageQueue( 2081): at android.app.ActivityThread$H.handleMessage(ActivityThread.java:2099)
W/MessageQueue( 2081): at android.os.Handler.dispatchMessage(Handler.java:99)
W/MessageQueue( 2081): at android.os.Looper.loop(Looper.java:123)
W/MessageQueue( 2081): at android.app.ActivityThread.main(ActivityThread.java:4627)
W/MessageQueue( 2081): at java.lang.reflect.Method.invokeNative(Native Method)
W/MessageQueue( 2081): at java.lang.reflect.Method.invoke(Method.java:521)
W/MessageQueue( 2081): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:868)
W/MessageQueue( 2081): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:626)
W/MessageQueue( 2081): at dalvik.system.NativeStart.main(Native Method)
It actually did sign me in once, and I got this from logcat:
Code:
D/skype ( 2081): Transport.connect fails. Sleeping for a second.
D/dalvikvm( 1011): GC_EXTERNAL_ALLOC freed 22734 objects / 1099360 bytes in 149ms
V/SID ( 2081): AVTransportWrapper (/tmp/pcm_from_skypekit_key): connected!
V/SID ( 2081): AVTransportWrapper (/tmp/pcm_to_skypekit_key): connected!
D/WifiService( 1011): ACTION_BATTERY_CHANGED pluggedType: 0
D/dalvikvm( 1011): GC_FOR_MALLOC freed 7222 objects / 347752 bytes in 114ms
I/ActivityManager( 1011): Starting activity: Intent { cmp=com.skype.raider/.ui.startup.FeatureTourActivity (has extras)
}
D/dalvikvm( 2081): GC_FOR_MALLOC freed 7362 objects / 509032 bytes in 34ms
I/dalvikvm( 2081): Uncaught exception thrown by finalizer (will be discarded):
I/dalvikvm( 2081): Ljava/lang/NullPointerException;:
I/dalvikvm( 2081): at com.skype.ipc.SkypeKitRunner.stopApp((null):-1)
I/dalvikvm( 2081): at com.skype.ipc.SkypeKitRunner.finalize((null):-1)
I/dalvikvm( 2081): at dalvik.system.NativeStart.run(Native Method)
E/MediaPlayerService( 906): create BoardHWPlayer
E/OMXPlayer( 906): Creating new NVOMXPlayer: 0x2b048
E/OMXPlayer( 906): 0x2b048 setDataSource url=droid://32:512404:72508
E/OMXPlayer( 906): render thread(14766) started: 0x2b048
E/OMXPlayer( 906): prepareAsync: 0x2b048
E/OMXPlayer( 906): prepare 0x2b048
E/OMXPlayer( 906): 0x2b048 Creating player for: droid://32:512404:72508
E/OMXPlayer( 906): prepare done 0x2b048
E/OMXPlayer( 906): render - signal wait 0x2b048
E/OMXPlayer( 906): start 0x2b048
E/OMXPlayer( 906): render - signal rx'd 0x2b048
D/dalvikvm( 1380): GC_EXPLICIT freed 10 objects / 368 bytes in 81ms
D/dalvikvm( 2081): GC_EXTERNAL_ALLOC freed 2280 objects / 159232 bytes in 28ms
I/ActivityManager( 1011): Displayed activity com.skype.raider/.ui.startup.FeatureTourActivity: 851 ms (total 851 ms)
E/OMXPlayer( 906): playback complete: 0x2b048
E/OMXPlayer( 906): playback complete - wait for signal 0x2b048
E/OMXPlayer( 906): reset: 0x2b048
D/ ( 906): setting block activity: 1
D/ ( 906): setting block activity: 0
E/OMXPlayer( 906): reset done 0x2b048
E/OMXPlayer( 906): destructor: 0x2b048
E/OMXPlayer( 906): playback complete - signal rx'd 0x2b048
E/OMXPlayer( 906): Worker Thread Exit -
D/ ( 910): NVRM_DAEMON(461): client process closed connection
D/ ( 910): NVRM_DAEMON(461): client process closed connection
D/ ( 910): NVRM_DAEMON(461): client process closed connection
E/OMXPlayer( 906): reset done 0x2b048
E/OMXPlayer( 906): destructor: 0x2b048 done
But then it crashed after the screen where it asks me if I want to sync all my contacts, and I said yes.
Code:
W/ActivityManager( 1011): Timeout executing service: ServiceRecord{4a787050 com.skype.raider/.service.SyncProviderServic
e}
I/Process ( 1011): Sending signal. PID: 2081 SIG: 3
I/dalvikvm( 2081): threadid=3: reacting to signal 3
I/dalvikvm( 2081): Wrote stack traces to '/data/anr/traces.txt'
I/Process ( 1011): Sending signal. PID: 1011 SIG: 3
I/dalvikvm( 1011): threadid=3: reacting to signal 3
I/dalvikvm( 1011): Wrote stack traces to '/data/anr/traces.txt'
I/Process ( 1011): Sending signal. PID: 14982 SIG: 3
I/dalvikvm(14982): threadid=3: reacting to signal 3
I/dalvikvm(14982): Wrote stack traces to '/data/anr/traces.txt'
I/Process ( 1011): Sending signal. PID: 1379 SIG: 3
I/dalvikvm( 1379): threadid=3: reacting to signal 3
I/dalvikvm( 1379): Wrote stack traces to '/data/anr/traces.txt'
I/Process ( 1011): Sending signal. PID: 1380 SIG: 3
I/dalvikvm( 1380): threadid=3: reacting to signal 3
I/dalvikvm( 1380): Wrote stack traces to '/data/anr/traces.txt'
I/Process ( 1011): Sending signal. PID: 2052 SIG: 3
I/dalvikvm( 2052): threadid=3: reacting to signal 3
I/dalvikvm( 2052): Wrote stack traces to '/data/anr/traces.txt'
I/Process ( 1011): Sending signal. PID: 14932 SIG: 3
I/dalvikvm(14932): threadid=3: reacting to signal 3
I/dalvikvm(14932): Wrote stack traces to '/data/anr/traces.txt'
I/Process ( 1011): Sending signal. PID: 1455 SIG: 3
I/dalvikvm( 1455): threadid=3: reacting to signal 3
I/dalvikvm( 1455): Wrote stack traces to '/data/anr/traces.txt'
I/Process ( 1011): Sending signal. PID: 1503 SIG: 3
I/dalvikvm( 1503): threadid=3: reacting to signal 3
I/dalvikvm( 1503): Wrote stack traces to '/data/anr/traces.txt'
I/Process ( 1011): Sending signal. PID: 14918 SIG: 3
I/dalvikvm(14918): threadid=3: reacting to signal 3
I/dalvikvm(14918): Wrote stack traces to '/data/anr/traces.txt'
I/Process ( 1011): Sending signal. PID: 14890 SIG: 3
I/dalvikvm(14890): threadid=3: reacting to signal 3
I/dalvikvm(14890): Wrote stack traces to '/data/anr/traces.txt'
I/Process ( 1011): Sending signal. PID: 14907 SIG: 3
I/dalvikvm(14907): threadid=3: reacting to signal 3
I/dalvikvm(14907): Wrote stack traces to '/data/anr/traces.txt'
I/Process ( 1011): Sending signal. PID: 14847 SIG: 3
I/dalvikvm(14847): threadid=3: reacting to signal 3
I/dalvikvm(14847): Wrote stack traces to '/data/anr/traces.txt'
I/Process ( 1011): Sending signal. PID: 20292 SIG: 3
I/dalvikvm(20292): threadid=3: reacting to signal 3
I/dalvikvm(20292): Wrote stack traces to '/data/anr/traces.txt'
I/Process ( 1011): Sending signal. PID: 1875 SIG: 3
I/dalvikvm( 1875): threadid=3: reacting to signal 3
I/dalvikvm( 1875): Wrote stack traces to '/data/anr/traces.txt'
I/Process ( 1011): Sending signal. PID: 5481 SIG: 3
I/dalvikvm( 5481): threadid=3: reacting to signal 3
I/dalvikvm( 5481): Wrote stack traces to '/data/anr/traces.txt'
I/Process ( 1011): Sending signal. PID: 5426 SIG: 3
I/dalvikvm( 5426): threadid=3: reacting to signal 3
I/dalvikvm( 5426): Wrote stack traces to '/data/anr/traces.txt'
I/Process ( 1011): Sending signal. PID: 1388 SIG: 3
I/dalvikvm( 1388): threadid=3: reacting to signal 3
I/dalvikvm( 1388): Wrote stack traces to '/data/anr/traces.txt'
I/Process ( 1011): Sending signal. PID: 1922 SIG: 3
I/dalvikvm( 1922): threadid=3: reacting to signal 3
I/dalvikvm( 1922): Wrote stack traces to '/data/anr/traces.txt'
I/Process ( 1011): Sending signal. PID: 3150 SIG: 3
I/dalvikvm( 3150): threadid=3: reacting to signal 3
I/dalvikvm( 3150): Wrote stack traces to '/data/anr/traces.txt'
I/Process ( 1011): Sending signal. PID: 3031 SIG: 3
I/dalvikvm( 3031): threadid=3: reacting to signal 3
I/dalvikvm( 3031): Wrote stack traces to '/data/anr/traces.txt'
I/Process ( 1011): Sending signal. PID: 3024 SIG: 3
I/dalvikvm( 3024): threadid=3: reacting to signal 3
I/dalvikvm( 3024): Wrote stack traces to '/data/anr/traces.txt'
I/Process ( 1011): Sending signal. PID: 3009 SIG: 3
I/dalvikvm( 3009): threadid=3: reacting to signal 3
I/dalvikvm( 3009): Wrote stack traces to '/data/anr/traces.txt'
I/Process ( 1011): Sending signal. PID: 30776 SIG: 3
I/dalvikvm(30776): threadid=3: reacting to signal 3
I/dalvikvm(30776): Wrote stack traces to '/data/anr/traces.txt'
I/Process ( 1011): Sending signal. PID: 30031 SIG: 3
I/dalvikvm(30031): threadid=3: reacting to signal 3
I/dalvikvm(30031): Wrote stack traces to '/data/anr/traces.txt'
I/Process ( 1011): Sending signal. PID: 1514 SIG: 3
I/dalvikvm( 1514): threadid=3: reacting to signal 3
I/dalvikvm( 1514): Wrote stack traces to '/data/anr/traces.txt'
I/Process ( 1011): Sending signal. PID: 1965 SIG: 3
I/dalvikvm( 1965): threadid=3: reacting to signal 3
I/dalvikvm( 1965): Wrote stack traces to '/data/anr/traces.txt'
E/ActivityManager( 1011): ANR in com.skype.raider
E/ActivityManager( 1011): Reason: Executing service com.skype.raider/.service.SyncProviderService
E/ActivityManager( 1011): Load: 0.34 / 0.16 / 0.16
E/ActivityManager( 1011): CPU usage from 10344ms to 11ms ago:
E/ActivityManager( 1011): system_server: 2% = 1% user + 1% kernel / faults: 87 minor 2 major
E/ActivityManager( 1011): y.mobile:remote: 0% = 0% user + 0% kernel / faults: 3256 minor
E/ActivityManager( 1011): ogle.android.gm: 0% = 0% user + 0% kernel / faults: 65 minor
E/ActivityManager( 1011): events/0: 0% = 0% user + 0% kernel
E/ActivityManager( 1011): e.process.gapps: 0% = 0% user + 0% kernel / faults: 56 minor 1 major
E/ActivityManager( 1011): android.browser: 0% = 0% user + 0% kernel / faults: 50 minor 1 major
E/ActivityManager( 1011): mmcqd: 0% = 0% user + 0% kernel
E/ActivityManager( 1011): droid.wallpaper: 0% = 0% user + 0% kernel / faults: 22 minor
E/ActivityManager( 1011): ft.keyboardplus: 0% = 0% user + 0% kernel / faults: 16 minor
E/ActivityManager( 1011): om.skype.raider: 0% = 0% user + 0% kernel / faults: 33 minor
E/ActivityManager( 1011): com.svox.pico: 0% = 0% user + 0% kernel / faults: 24 minor
E/ActivityManager( 1011): nie.geniewidget: 0% = 0% user + 0% kernel / faults: 64 minor
E/ActivityManager( 1011): viders.calendar: 0% = 0% user + 0% kernel / faults: 23 minor
E/ActivityManager( 1011): TOTAL: 9% = 2% user + 2% kernel + 0% iowait + 4% softirq
D/skia ( 1011): purging 193K from font cache [25 entries]
Force closed Skype, restarted it, and got this:
Code:
I/ActivityManager( 1011): Starting activity: Intent { act=android.intent.action.MAIN cat=[android.intent.category.LAUNCH
ER] flg=0x10200000 cmp=com.skype.raider/.ui.SplashScreenActivity }
I/ActivityManager( 1011): Start proc com.skype.raider for activity com.skype.raider/.ui.SplashScreenActivity: pid=17662
uid=10057 gids={3003, 1015}
D/dalvikvm(17662): Debugger has detached; object registry had 1 entries
D/dalvikvm(17662): GC_FOR_MALLOC freed 2011 objects / 137984 bytes in 30ms
I/ActivityManager( 1011): Starting activity: Intent { cmp=com.skype.raider/.ui.startup.IntroToSkypeActivity (has extras)
}
I/ActivityManager( 1011): Starting activity: Intent { flg=0x4000000 cmp=com.skype.raider/.ui.startup.SignInActivity (has
extras) }
W/Resources(17662): Converting to string: TypedValue{t=0x12/d=0x0 a=2 r=0x7f0d0021}
W/Resources(17662): Converting to string: TypedValue{t=0x12/d=0x0 a=2 r=0x7f0d0021}
D/FlurryAgent(17662): Starting new session
D/FlurryAgent(17662): Sending report to: http://data.flurry.com/aar.do
I/Process (17662): Sending signal. PID: 14594 SIG: 9
I/Process (17662): Sending signal. PID: 14598 SIG: 9
I/Process (17662): Sending signal. PID: 14600 SIG: 9
I/Process (17662): Sending signal. PID: 14601 SIG: 9
I/Process (17662): Sending signal. PID: 14602 SIG: 9
I/Process (17662): Sending signal. PID: 14604 SIG: 9
I/Process (17662): Sending signal. PID: 14605 SIG: 9
I/Process (17662): Sending signal. PID: 14606 SIG: 9
I/Process (17662): Sending signal. PID: 14608 SIG: 9
I/Process (17662): Sending signal. PID: 14619 SIG: 9
I/Process (17662): Sending signal. PID: 14757 SIG: 9
I/global (17662): Default buffer size used in BufferedInputStream constructor. It would be better to be explicit if an
8k buffer is required.
D/dalvikvm(17662): GC_FOR_MALLOC freed 3538 objects / 234272 bytes in 36ms
D/skype (17662): Transport.connect fails. Sleeping for a second.
D/dalvikvm( 1011): GC_EXTERNAL_ALLOC freed 20621 objects / 1039464 bytes in 122ms
D/FlurryAgent(17662): Report successful
I/ActivityManager( 1011): Displayed activity com.skype.raider/.ui.startup.SignInActivity: 1014 ms (total 2835 ms)
D/dalvikvm(17662): Trying to load lib /data/data/com.skype.raider/lib/libpcmhost.so 0x4a59e608
D/dalvikvm(17662): Added shared lib /data/data/com.skype.raider/lib/libpcmhost.so 0x4a59e608
V/SID (17662): AVTransportWrapper (/tmp/pcm_from_skypekit_key): connected!
V/SID (17662): AVTransportWrapper (/tmp/pcm_to_skypekit_key): connected!
D/skia ( 1011): purging 196K from font cache [26 entries]
D/dalvikvm( 3024): GC_EXPLICIT freed 451 objects / 19984 bytes in 57ms
D/WifiService( 1011): ACTION_BATTERY_CHANGED pluggedType: 0
D/dalvikvm(14847): GC_EXPLICIT freed 5798 objects / 776232 bytes in 75ms
D/dalvikvm( 1455): GC_EXPLICIT freed 533 objects / 25688 bytes in 69ms
D/dalvikvm( 1388): GC_EXPLICIT freed 470 objects / 45040 bytes in 84ms
And got the following ANR trace that I sent to Skype. It's attached to this post.
Click to expand...
Click to collapse
lifeisfun said:
Working fine for me on vegan 5.1
Click to expand...
Click to collapse
Which kernel are you using? do you have swype running?
Working fine on my Vegan 5.1, no Swype, headphone volume patch.
festivus said:
Working fine on my Vegan 5.1, no Swype, headphone volume patch.
Click to expand...
Click to collapse
I suspect is the swype mod that is causing it. TomorrowI will test it
vectorcharlie said:
Which rom/kernel re you using? is this a vegan 5.1 problem? I am vegan 5.1.with clemsys latest
Click to expand...
Click to collapse
Pretty much the same as me, except I'm also using the data2loop mod as well.
vectorcharlie said:
I suspect is the swype mod that is causing it. TomorrowI will test it
Click to expand...
Click to collapse
Except I don't have swype either.
I suspect is the swype mod that is causing it. TomorrowI will test it
Click to expand...
Click to collapse
I can confirm that the build.prop edit that enables the swype dictionary breaks skype logon. Dr. Seuss would have a field day with this!
I've toggled it back and forth without rebooting on both Clemsyn's and Pershoot's kernels. Skype is reading build.prop and it pisses me off, because that breaks Swype!!!
And also I do not like green eggs and spam...
Cheers,
geek111
<edit> Spam Spam Spam Locks, Bagels and Spam!!!</edit>
I'm having the same problem with Skype not logging in but I'm not using Swype at all. So that may be the problem for some but it's not the only smoking gun. I am running Clemsyns latest kernel so I'll try some different ones later tonight to try and isolate this.
Sent from my VEGAn-TAB-v1.0.0B5.1 using Tapatalk
FWIW I note there are two versions of the apk file available from many sources. On my tablet the version named ending with "beta" fails every time. The non-beta apk works without any problem. It's missing video, but perhaps their programmers will eventually upgrade the app.
Tom
fyyzer said:
I'm having the same problem with Skype not logging in but I'm not using Swype at all. So that may be the problem for some but it's not the only smoking gun. I am running Clemsyns latest kernel so I'll try some different ones later tonight to try and isolate this.
Sent from my VEGAn-TAB-v1.0.0B5.1 using Tapatalk
Click to expand...
Click to collapse
It's not swype per-se that breaks Skype for me.
It's the /system/build.prop edit that fixes the Swype dictionary which breaks Skype. (The 'swype specific' build.prop line fools software into thinking that the G-tab is a Samsung...)
For Skype to work the ro.build.fingerprint may need to be set to-
Code:
ro.build.fingerprint=google/passion/passion/mahimahi:2.2/FRF91/43546:user/release-keys
(a la market fix...)
You might want to post your existing 'fingerprint' value so we can compare and see if that's the culprit 4 sure.
Hope this helps,
geek111
p.s.- DON'T MODIFY YOUR /system/build.prop FILE WITHOUT BACKING IT UP!!! YOU HAVE BEEN WARNED.
P.P.S.- Just reflashed to make sure... Skype works for me on both Clemsyn's and Pershoot's kernels as long as the fingerprint line is as above. I change it, and Skype hangs during logon... Kinda lame that both apps are parsing that line.
i am running cm7 beta1 (the one in clockworkmod)with swype and skype works fine...i think it has to do with the fact that the phone parts have been removed because i was on bitrixs cm7 and it doesnt work and on the beta (and in the ultimatedroid rom which has the phone parts) it does.... ( havent used vegan tab but the above workaround could work for bitrixs cm7)
tom62015 said:
( havent used vegan tab but the above workaround could work for bitrixs cm7)
Click to expand...
Click to collapse
DON'T DO THAT!!!
That fingerprint is for Android 2.2. CM7 is 2.3.
You WILL break your system if you do that on CM7.
cheers,
geek111
I recently updated my Nexus 6 to 5.1 and while using the camera I noticed it wasn't rotating the controls with the phone. I did some further testing and realized that auto-rotate wasn't working either; I tried toggling the setting, but it still didn't work. Doing a factory reset and re-flashing 5.1 also did nothing. I finally tried flashing 5.0.1, and suddenly everything was working, but returning to 5.1 broke everything again. The Accelerometer Monitor app shows no data at all, so it appears the accelerometer is completely dead in 5.1.
Is anyone else having this issue? Is there any way I can fix it besides downgrading to 5.0.1?
I guess that also explains why it seemed like ambient display wasn't activating when I picked up the phone...
Update: Turns out, none of the sensors are working -- accelerometer, compass, light, proximity, etc... the sensor apps in the Play Store say they don't even exist.
Update 2: Sensors are working in the Android M preview.
Accelerometer is still broken in the new LMY47E build. Am I really the only one who has run into this problem? Should I contact Motorola for a new phone?
I have only seen you report the problem. I recall a post long time ago where someone dropped there phone and it got jammed. The smacked it on the corner and it came loose. Not suggesting you do that just telling you what I have seen.
TonikJDK said:
I have only seen you report the problem. I recall a post long time ago where someone dropped there phone and it got jammed. The smacked it on the corner and it came loose. Not suggesting you do that just telling you what I have seen.
Click to expand...
Click to collapse
Hmm, odd. Yeah, I came across that thread while searching for other posts about it. I tried their solution with no luck, sadly. However, as I stated in the first post, the accelerometer works if I flash the 5.0.1 factory image, so I'm pretty sure it's not broken/stuck hardware.
I have this exact problem too. Did you find any solution? I don't want to send my phone to the repair service again...
Floken said:
I have this exact problem too. Did you find any solution? I don't want to send my phone to the repair service again...
Click to expand...
Click to collapse
I still haven't found a solution. I've tried all the 5.1 builds that are available from Google (LMY47D, LMY47E, LMY47I) and the issue exists in all of them. I've considered contacting Motorola to see what they could do for me, but I haven't got a chance to do it yet.
I'm on 5.1 E and it works fine for me..
Maybe one of the 5.1 based custom roms?
For what it's worth, this is what I get in the system log when I try to use an app that uses the accelerometer or other orientation sensors:
Code:
04-01 14:23:40.112 1883 1904 E qti_sensors_hal: processBufferingResp: Result: 1, Error: 5
04-01 14:23:40.112 1883 1904 E qti_sensors_hal: processBufferingResp: 0 Error: 4 Reason: 18
04-01 14:23:40.112 1883 2865 E qti_sensors_hal: enable:sensor(android.sensor.accelerometer) Failed for handle 0 @ samp 50 Hz rpt 0 Hz batched 0
04-01 14:23:40.112 1883 2865 E qti_sensors_hal: Activate the handle 0 is not successful
04-01 14:23:40.112 1883 2865 E SensorService: Error activating sensor 0 (Operation not permitted)
04-01 14:23:40.115 1883 1904 E qti_sensors_hal: processBufferingResp: Result: 1, Error: 5
04-01 14:23:40.115 1883 1904 E qti_sensors_hal: processBufferingResp: 10 Error: 4 Reason: 18
04-01 14:23:40.116 1883 1898 E qti_sensors_hal: enable:sensor(android.sensor.magnetic_field) Failed for handle 10 @ samp 50 Hz rpt 0 Hz batched 0
04-01 14:23:40.116 1883 1898 E qti_sensors_hal: Activate the handle 10 is not successful
04-01 14:23:40.116 1883 1898 E SensorService: Error activating sensor 10 (Operation not permitted)
Floken said:
Maybe one of the 5.1 based custom roms?
Click to expand...
Click to collapse
I think I'll try one of those when I get a chance and see if it's fixed there.
Edit: It doesn't work in the latest Chroma ROM at least (LMY47I based)
Interestingly, the sensors seem to be working again in the preview version of Android M...
Does anyone knows why my logcat has repeating
Code:
I/ART Starting a blocking GC xposed
in logcat? It repeats itself for 10-20 times every few seconds.
Everything works okay though, but I couldn't help feeling that the phone could perform better if I eliminate subtle issues.
I am using Xposed 89 on Nougat (HTC M9/arm64 using ViperROM).