Related
Calendar fails to load 'today', and in settings, cannot load calendars. Not a Microsoft Exchange issue (I don't use it).
Has anyone else had this problem? I searched around and found the exact same problem with the original Desire in another forum.
I'm: Asian Sense, rooted, Clockwork
Must just be yours. Mine's fine: Bell, stock, unrooted.
I just took a look in the log, and here's where I think the problem shows up:
11-22 16:39:25.055 I/ActivityManager( 1306): Starting activity: Intent { act=android.intent.action.VIEW cmp=com.htc.calendar/.ManageCalendarsActivity }
11-22 16:39:25.125 V/WindowManager( 1306): Remove Window{47bfb6b0 AtchDlg:com.htc.calendar/com.htc.calendar.MonthActivity paused=false}: mSurface=Surface(name=AtchDlg:com.htc.calendar/com.htc.calendar.MonthActivity, identity=13) mExiting=false isAnimating=true app-a[email protected]47a63f30 inPendingTransaction=true mDisplayFrozen=false
11-22 16:39:25.135 E/WindowManager( 1306): return in removeWindowLocked
11-22 16:39:25.495 E/ActivityThread( 2253): Failed to find provider info for com.android.calendar
11-22 16:39:29.025 E/ActivityThread( 1724): Failed to find provider info for com.android.calendar
Hi,
I modified the recently leaked skype w/ video app for the HTC Thunderbolt. Let me document my changes and progress so far:
Here is the original app:http://www.droid-life.com/2011/04/11/download-skype-with-video-on-android/
1) if you try to install the app unmodified on a non HTC thunderbolt phone, you will get an "installation failed" message. I decompiled the app using these instructions: http://jack-mannino.blogspot.com/2010/09/reversing-android-apps-101.html
2) I modified the AndroidManifest.xml to remove this line:
<uses-library android:name="com.htc.device" />
3) I then recompiled and resigned the app( http://www.addictivetips.com/mac-os/auto-sign-tool-for-android-developers-on-mac/).
4) The apk now installed on my Nexus S but I get this error when I opened it:
"Sorry, your phone is not able to use this version of Skype. To find out more about Skype on mobile, visit www.skype.com"
5) I looked through the code and found the offending text in com.skype.ui.SplashScreenActivity.class:
protected void onResume()
{
super.onResume();
if (!f.a())
{
Toast.makeText(this, "Sorry, your phone is not able to use this version of Skype. To find out more about Skype on mobile, visit www.skype.com", 1).show();
finish();
}
.....
I commented out the toast and finish() line and then recompiled and resigned.
6) The apk installs but crashes when I try to open it:
W/dalvikvm(17595): VFY: bad arg 1 (into Ljava/lang/CharSequence
W/dalvikvm(17595): VFY: rejecting call to Landroid/widget/Toast;.makeText (Landroid/content/Context;Ljava/lang/CharSequence;I)Landroid/widget/Toast;
W/dalvikvm(17595): VFY: rejecting opcode 0x71 at 0x0010
W/dalvikvm(17595): VFY: rejected Lcom/skype/merlin_mecha/ui/SplashScreenActivity;.onResume ()V
W/dalvikvm(17595): Verifier rejected class Lcom/skype/merlin_mecha/ui/SplashScreenActivity;
W/dalvikvm(17595): Class init failed in newInstance call (Lcom/skype/merlin_mecha/ui/SplashScreenActivity
D/AndroidRuntime(17595): Shutting down VM
W/dalvikvm(17595): threadid=1: thread exiting with uncaught exception (group=0x40015560)
E/AndroidRuntime(17595): FATAL EXCEPTION: main
E/AndroidRuntime(17595): java.lang.VerifyError: com.skype.merlin_mecha.ui.SplashScreenActivity
E/AndroidRuntime(17595): at java.lang.Class.newInstanceImpl(Native Method)
E/AndroidRuntime(17595): at java.lang.Class.newInstance(Class.java:1409)
E/AndroidRuntime(17595): at android.app.Instrumentation.newActivity(Instrumentation.java:1021)
E/AndroidRuntime(17595): at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:1681)
E/AndroidRuntime(17595): at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:1793)
E/AndroidRuntime(17595): at android.app.ActivityThread.access$1500(ActivityThread.java:123)
E/AndroidRuntime(17595): at android.app.ActivityThread$H.handleMessage(ActivityThread.java:939)
E/AndroidRuntime(17595): at android.os.Handler.dispatchMessage(Handler.java:99)
E/AndroidRuntime(17595): at android.os.Looper.loop(Looper.java:123)
E/AndroidRuntime(17595): at android.app.ActivityThread.main(ActivityThread.java:3848)
E/AndroidRuntime(17595): at java.lang.reflect.Method.invokeNative(Native Method)
E/AndroidRuntime(17595): at java.lang.reflect.Method.invoke(Method.java:507)
E/AndroidRuntime(17595): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:841)
E/AndroidRuntime(17595): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:599)
E/AndroidRuntime(17595): at dalvik.system.NativeStart.main(Native Method)
W/ActivityManager( 176): Force finishing activity com.skype.merlin_mecha/.ui.SplashScreenActivity
W/ActivityManager( 176): Force finishing activity info.tikuwarez.launcher3/.ClassicAppPicker
This is my progress so far and here is my modified apk:http://www.mediafire.com/?l6xddlun3u52ung
Does this enable the use of the back camera instead of the front?
For my wife's fascinate
Sent from my ADR6400L using XDA Premium App
@eyeburn : Thanks for the investigation.
Could you try to remove the " if statement " instead ?
I guess the shared library is not only for security, but we will see that later.
More updates. I looked at the SplashScreenActivity.smali code and removed this line:
invoke-virtual {p0}, Lcom/skype/merlin_mecha/ui/SplashScreenActivity;->finish()V
this basically disables the the exiting(the finish() in the code below) of the program during the verizon phone check.
Now the phone doesn't crash but just stays at the "skype mobile" splash screen with the skype background.
I'll look at this again tomorrow. Gonna sleep now.
Updated apk as of midnight Apr 12: http://www.mediafire.com/?eqgr111a7agg3qv
My current thinking is the app is stuck in this while loop:
protected void onResume()
{
super.onResume();
if (!f.a())
{
Toast.makeText(this, "Sorry, your phone is not able to use this version of Skype. To find out more about Skype on mobile, visit www.skype.com", 1).show();
finish();
}
while (true)
{
return;
Intent localIntent1 = new Intent(this, SignInActivity.class);
boolean bool1 = getIntent().getBooleanExtra("LaunchedBySyncAdapter", 0);
Intent localIntent2 = localIntent1.putExtra("LaunchedBySyncAdapter", bool1);
int i = getIntent().getIntExtra("PostLoginCommand", 0);
Intent localIntent3 = localIntent1.putExtra("PostLoginCommand", i);
String str = getIntent().getStringExtra("PostLoginDataUri");
Intent localIntent4 = localIntent1.putExtra("PostLoginDataUri", str);
ac localac = new ac(this, localIntent1);
monitorenter;
try
{
this.a = localac;
Handler localHandler = this.b;
Runnable localRunnable = this.a;
boolean bool2 = localHandler.postDelayed(localRunnable, 1500L);
monitorexit;
continue;
}
finally
{
localObject = finally;
monitorexit;
}
}
throw localObject;
}
}
I keep getting this messages on my logcat:
I/TelephonyRegistry( 176): notifyServiceState: 0 home T - Mobile T - Mobile 310260 UMTS CSS not supported -1 -1RoamInd: -1DefRoamInd: -1EmergOnly: false
I/TelephonyRegistry( 176): notifyDataConnection: state=2 isDataConnectivityPossible=true reason=null interfaceName=rmnet0 networkType=3
I/TelephonyRegistry( 176): notifyServiceState: 0 home T - Mobile T - Mobile 310260 HSDPA CSS not supported -1 -1RoamInd: -1DefRoamInd: -1EmergOnly: false
I/TelephonyRegistry( 176): notifyDataConnection: state=2 isDataConnectivityPossible=true reason=null interfaceName=rmnet0 networkType=8
More likely, that you killed the login intent, which supposed to invoke login activity. You already have 'return' as the first statement of the while loop. The code in it's current state doesn't make sense to me. It should be an exist condition from the loop, otherwise the only way to exit the loop is via exception, which will effectively kill the application.
ivan.volosyuk said:
More likely, that you killed the login intent, which supposed to invoke login activity. You already have 'return' as the first statement of the while loop. The code in it's current state doesn't make sense to me. It should be an exist condition from the loop, otherwise the only way to exit the loop is via exception, which will effectively kill the application.
Click to expand...
Click to collapse
same conclusion here, but I assume this part of code is badly decompiled. There are several other while->true->return in this code.
I/ActivityManager( 176): Starting: Intent { act=android.settings.APPLICATION_DETAILS_SETTINGS dat=package:com.skype.merlin_mecha cmp=com.android.settings/.applications.InstalledAppDetails } from pid 18780
D/dalvikvm(18780): GC_CONCURRENT freed 333K, 48% free 3339K/6343K, external 5923K/6893K, paused 67ms+23ms
I/ActivityManager( 176): Displayed com.android.settings/.applications.InstalledAppDetails: +1s756ms
D/szipinf (18780): Initializing inflate state
D/szipinf (18780): Initializing inflate state
D/szipinf (18780): Initializing inflate state
D/szipinf (18780): Initializing inflate state
D/szipinf (18780): Initializing inflate state
D/szipinf (18780): Initializing inflate state
D/szipinf (18780): Initializing inflate state
D/szipinf (18780): Initializing inflate state
I/Process ( 176): Sending signal. PID: 18721 SIG: 9
I/ActivityManager( 176): Force stopping package com.skype.merlin_mecha uid=10068
I/ActivityManager( 176): Force finishing activity HistoryRecord{4057dcc8 com.skype.merlin_mecha/.ui.SplashScreenActivity}
W/InputManagerService( 176): Window already focused, ignoring focus gain of: [email protected]
E/InputDispatcher( 176): channel '407ae0c0 com.skype.merlin_mecha/com.skype.merlin_mecha.ui.SplashScreenActivity (server)' ~ Consumer closed input channel or an error occurred. events=0x8
E/InputDispatcher( 176): channel '407ae0c0 com.skype.merlin_mecha/com.skype.merlin_mecha.ui.SplashScreenActivity (server)' ~ Channel is unrecoverably broken and will be disposed!
I/WindowManager( 176): WIN DEATH: Window{407ae0c0 com.skype.merlin_mecha/com.skype.merlin_mecha.ui.SplashScreenActivity paused=true}
This is what is happening now.
Keep up the good work, a LOT of people will love you if you can get this to work on other phones like the Galaxy S.
Agreed keep up the good work....and Thanks
speaking as someone with a G Tablet, I really want this to work, so please take all the encouragement i can offer!
Keep up the good work.
Oh thank you.
Seriously, I posted about how somebody should modify this to work on all phones yesterday.
As for me, I'm getting "Sorry1, your phone is not able to use this version of skype"
(Wonder why it says "Sorry1")
I'm using a mytouch 4g with cm7 stable
Working on the same thing here on my EVO. I tried your APK but I don't get to the sign-in screen. I removed the same line from the AndroidManifest.xml file that you did so that it would install. I took a different approach and modified the VerizonNetwork and VerizonMerlin check to return 0x1 instead of 0x0 so that it gets by the Toast successfully and I get the sign-in screen. Now after I sign-in, the service crashes.
Code:
I/com.skype.merlin_mecha.service.a(17177): system board:supersonic bootloader:2.10.0001 brand:sprint product:htc_supersonic model:PC36100 manufacturer:HTC device:supersonic display:3.70.651.1 fingerprint:sprint/htc_supersonic/supersonic/supersonic:2.2/FRF91/294884:user/release-keys host:AA109 user:root radio:2.15.00.09.01 tags:release-keys type:user
I/global (17177): Default buffer size used in BufferedInputStream constructor. It would be better to be explicit if an 8k buffer is required.
D/dalvikvm(17177): GC_FOR_MALLOC freed 5340 objects / 712528 bytes in 124ms
I/LSState (12428): EventReceiver:android.intent.action.NOTIFICATION_UPDATE
I/StartSkypeKitOperation(17177): REMOVE THIS ONCE VERIFIED: appToken = KdXVSo6qB9
I/dalvikvm(17177): Jit: resizing JitTable from 4096 to 8192
D/dalvikvm(15756): GC_EXPLICIT freed 3901 objects / 412584 bytes in 100ms
I/ActivityManager(12428): Process com.skype.merlin_mecha (pid 17177) has died.
W/ActivityManager(12428): Scheduling restart of crashed service com.skype.merlin_mecha/.service.SkypeServiceController in 5000ms
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
http://db.tt/umgHYVq
-Daryel
daryel - i tried it and the same happened to me, but there was nothing that said the app force-closed. it simply closed itself and that was that.
it looks like real headway is being made here. I will faithfully watch this until it is finished
oh the sorry1 was a debugging thing hehe.
so it is now crashing in com.skype.merlin_mecha.service.a
Looks to be failing some fingerprint checking. I guess this is where it verifies the phone.
I wonder which file this line is coming from:
I/StartSkypeKitOperation(17177): REMOVE THIS ONCE VERIFIED: appToken = KdXVSo6qB9
New Edit:
Ok the verification is done in com.skype.merlin_mecha.startup.SignInActivity.
I am speculating, the check and crash is in:
protected void onCreate(Bundle paramBundle)
Thanks guys, it looks like you are pretty close to the solution.
Finger crossed
daryelv said:
Working on the same thing here on my EVO. I tried your APK but I don't get to the sign-in screen. I removed the same line from the AndroidManifest.xml file that you did so that it would install. I took a different approach and modified the VerizonNetwork and VerizonMerlin check to return 0x1 instead of 0x0 so that it gets by the Toast successfully and I get the sign-in screen. Now after I sign-in, the service crashes.
Click to expand...
Click to collapse
Sorry but where is this Verizon check?
There are 2 .so missing.
if you look in a/a/a.smali you will find a ref to
/data/data/com.skype.merlin_mecha/lib/libskype_jni.so
And com\skype\a\c.smali has a ref to /data/data/com.test.java_surface/lib/libskype_jni.so
that means there is more to this
eyeburn said:
I wonder which file this line is coming from:
I/StartSkypeKitOperation(17177): REMOVE THIS ONCE VERIFIED: appToken = KdXVSo6qB9
Click to expand...
Click to collapse
Looks like this comes from com\skype\merlin_mecha\service\bs.class
Code:
Object localObject = "M9QA6f6YIH";
if (!com.skype.merlin_mecha.a.b.b)
continue;
if (!com.skype.merlin_mecha.a.b.a)
continue;
localObject = "KdXVSo6qB9";
String str4 = "REMOVE THIS ONCE VERIFIED: appToken = " + (String)localObject;
int k = Log.i("StartSkypeKitOperation", str4);
bo.g(this.c).SetApplicationToken((String)localObject);
boolean bool1 = bo.c(this.c);
if (bool1)
continue;
OK so I have Magic 2014 on my tablet, version 1.2.0. I installed it from Amazon Appstore because it worked, whereas Play Store kept throwing errors at me while downloading the extra content. And hence, the in-app content purchases I've made have also been through Amazon.
This evening I tried upgrading the app to 1.4.0 from Amazon. It went through the entire 1.5 GB download, commenced the install... and then promptly rebooted. The app is still sitting at version 1.2.0.
I found the apk file cached in /sdcard/Android/data/files/apks. So I attempted to install from there. Again after about a minute it rebooted.
So, next, I monitored with adb logcat while doing the install. There was a lot of gunk in the log from other apps, so I tried again while enabling Developer Options "Don't keep activities". It was still too much text to monitor in a Command Prompt window, so I tried one more time using:
adb logcat > magic-crash.txt
to save in a text file. Here are the critical moments:
I/ActivityManager( 8603): START u0 {act=android.intent.action.VIEW dat=file:///storage/emulated/0/Android/data/com.amazon.venezia/files/apks/f13e69c1-0c52-489c-95bc-ae7d0475afaf.apk typ=application/vnd.android.package-archive cmp=com.android.packageinstaller/.PackageInstallerActivity} from pid 17478
I/ActivityManager( 8603): Start proc com.android.packageinstaller for activity com.android.packageinstaller/.PackageInstallerActivity: pid=17705 uid=10044 gids={50044, 1028}
I/ActivityManager( 8603): START u0 {dat=file:///storage/emulated/0/Android/data/com.amazon.venezia/files/apks/f13e69c1-0c52-489c-95bc-ae7d0475afaf.apk cmp=com.android.packageinstaller/.InstallAppProgress (has extras)} from pid 17705
I/ActivityManager( 8603): Start proc com.android.defcontainer for service com.android.defcontainer/.DefaultContainerService: pid=17730 uid=10013 gids={50013, 1028, 1015, 1023, 2001}
W/ActivityManager( 8603): No content provider found for permission revoke: file:///storage/emulated/0/Android/data/com.amazon.venezia/files/apks/f13e69c1-0c52-489c-95bc-ae7d0475afaf.apk
I/ActivityManager( 8603): Start proc com.android.vending for broadcast com.android.vending/com.google.android.vending.verifier.PackageVerificationReceiver: pid=17744 uid=10047 gids={50047, 3003, 1028, 1015}
I/PackageManager( 8603): Verification timed out for file:///storage/emulated/0/Android/data/com.amazon.venezia/files/apks/f13e69c1-0c52-489c-95bc-ae7d0475afaf.apk
I/PackageManager( 8603): Continuing with installation of file:///storage/emulated/0/Android/data/com.amazon.venezia/files/apks/f13e69c1-0c52-489c-95bc-ae7d0475afaf.apk
W/Watchdog( 8603): *** WATCHDOG KILLING SYSTEM PROCESS: Blocked in handler on PackageManager (PackageManager)
W/Watchdog( 8603): PackageManager stack trace:
W/Watchdog( 8603): at android.os.BinderProxy.transact(Native Method)
W/Watchdog( 8603): at com.android.internal.app.IMediaContainerService$Stub$Proxy.copyResource(IMediaContainerService.java:290)
W/Watchdog( 8603): at com.android.server.pm.PackageManagerService$FileInstallArgs.copyApk(PackageManagerService.java:7953)
W/Watchdog( 8603): at com.android.server.pm.PackageManagerService$PackageHandler.doHandleMessage(PackageManagerService.java:960)
W/Watchdog( 8603): at com.android.server.pm.PackageManagerService$PackageHandler.handleMessage(PackageManagerService.java:593)
W/Watchdog( 8603): at android.os.Handler.dispatchMessage(Handler.java:102)
W/Watchdog( 8603): at android.os.Looper.loop(Looper.java:137)
W/Watchdog( 8603): at android.os.HandlerThread.run(HandlerThread.java:61)
W/Watchdog( 8603): *** GOODBYE!
Does this give any clues to why this won't install without rebooting?
Incidentally I also tried to copy the 1.5 GB apk to my desktop and use "adb install -r". However I get this:
could not allocate buffer for 'magic140.apk'
rm failed for /data/local/tmp/magic140.apk, No such file or directory
Incidentally, I also tried taking a Titanium Backup of the 1.2.0 app and restoring the same version over top of itself. This, too, prompted a reboot with a similar logcat message.
Sent from my Nexus 5 using Tapatalk
Any advice would be appreciated. The same apk has no trouble installing on Nexus 5.
Sent from my Nexus 5 using Tapatalk
Update: I ended up going the brute force route. In TWRP recovery I replaced the existing APK version in /data/app/ with the new one, renamed it appropriately, applied chmod 644 and chown system.system to match. Starting it up now to see if that did the trick. Appears to work.
Hi,
I recently updated my Galaxy S4 (GT-I9505) to the latest firmware (I9505XXUHOA7 (OXA) - Android 5.0.1).
Since, I cannot connect the phone to the car.
Actually, the pairing is ok, but when the car tries to sync phonebook (automatically), the bluetooth service crash and restart.
I can say that because I made a test. Immediately after the connection I started a call manually and the call was made without any problem, but when I ended the call, the bluetooth service crashed...
(There was no problems with the 4.4.2)
My receiver is the Alpine CDE-125BT
Some logs here :
Code:
I/ActivityManager( 995): Force stopping com.android.bluetooth appid=1002 user=0: clear data
I/ActivityManager( 995): Killing 1524:com.android.bluetooth/1002 (adj -11): stop com.android.bluetooth
W/ActivityManager( 995): Scheduling restart of crashed service com.android.bluetooth/.gatt.GattService in 1000ms
W/ActivityManager( 995): Scheduling restart of crashed service com.android.bluetooth/.btservice.AdapterService in 11000ms
D/PackageManager( 995): remove MCS_UNBIND message and Posting MCS_UNBIND 10 secs later
I/ActivityManager( 995): Force stopping service ServiceRecord{c65127b u0 com.android.bluetooth/.btservice.AdapterService}
I/ActivityManager( 995): Force stopping service ServiceRecord{1e18793f u0 com.android.bluetooth/.gatt.GattService}
I/ActivityManager( 995): Force stopping com.android.bluetooth appid=1002 user=0: clear data
W/ResourcesManager(12103): Asset path '/system/framework/com.android.media.remotedisplay.jar' does not exist or contains no resources.
W/ResourcesManager(12103): Asset path '/system/framework/com.android.location.provider.jar' does not exist or contains no resources.
I/ActivityManager( 995): Start proc com.android.bluetooth for service com.android.bluetooth/.btservice.AdapterService: pid=12125 uid=1002 gids={41002, 9997, 3003, 3002, 3001, 1028, 1015, 1023, 3005, 1016, 3008} abi=armeabi-v7a
D/SSRM:n ( 995): SIOP:: AP = 420, CUR = 460
W/ResourcesManager(12125): Asset path '/system/framework/javax.obex.jar' does not exist or contains no resources.
W/ResourcesManager(12125): Asset path '/system/framework/com.broadcom.bt.jar' does not exist or contains no resources.
W/ResourcesManager(12119): Asset path '/system/framework/secsmartcard.jar' does not exist or contains no resources.
W/ContextImpl( 1465): Calling a method in the system process without a qualified user: android.app.ContextImpl.sendBroadcast:1699 android.content.ContextWrapper.sendBroadcast:391 com.android.settings.nfc.SBeamEnabler.updateState:878 com.android.settings.nfc.SBeamEnabler.saveSbeamOn:869 com.android.settings.nfc.SBeamEnabler.procOnResume:196
W/ContextImpl( 1465): Calling a method in the system process without a qualified user: android.app.ContextImpl.startService:2064 android.content.ContextWrapper.startService:533 com.android.settings.nearby.NearbyEnabler.startDmsService:551 com.android.settings.nearby.NearbyEnabler.resume:318 com.android.settings.Settings$HeaderAdapter.resume:5054
W/ContextImpl( 1465): Calling a method in the system process without a qualified user: android.app.ContextImpl.bindService:2137 android.content.ContextWrapper.bindService:559 com.android.settings.nearby.NearbyEnabler.startDmsService:553 com.android.settings.nearby.NearbyEnabler.resume:318 com.android.settings.Settings$HeaderAdapter.resume:5054
W/ContextImpl( 995): Calling a method in the system process without a qualified user: android.app.ContextImpl.sendBroadcast:1699 com.android.server.InputMethodManagerService$6.run:2733 java.lang.Thread.run:818 <bottom of call stack> <bottom of call stack>
W/ContextImpl( 995): Calling a method in the system process without a qualified user: android.app.ContextImpl.sendBroadcast:1699 com.android.server.SEDenialService$AuditFileObserver.onEvent:76 android.os.FileObserver$ObserverThread.onEvent:122 android.os.FileObserver$ObserverThread.observe:-2 android.os.FileObserver$ObserverThread.run:85
W/ResourcesManager(12278): Asset path '/system/framework/com.google.android.media.effects.jar' does not exist or contains no resources.
W/ResourcesManager(12278): Asset path '/system/framework/com.google.android.maps.jar' does not exist or contains no resources.
W/ResourcesManager(12278): Asset path '/system/framework/com.broadcom.nfc.jar' does not exist or contains no resources.
W/ResourcesManager(12278): Asset path '/system/framework/org.simalliance.openmobileapi.jar' does not exist or contains no resources.
W/ResourcesManager(24168): Asset path '/system/framework/com.google.android.media.effects.jar' does not exist or contains no resources.
W/ContextImpl( 995): Calling a method in the system process without a qualified user: android.app.ContextImpl.sendBroadcast:1699 com.android.server.SEDenialService$AuditFileObserver.onEvent:76 android.os.FileObserver$ObserverThread.onEvent:122 android.os.FileObserver$ObserverThread.observe:-2 android.os.FileObserver$ObserverThread.run:85
E/auditd ( 2330): In denial and Property audit_ondenial is set to 1
I/ActivityManager( 995): Killing 4018:com.android.providers.calendar/u0a48 (adj 15): BG, 5562K, hotnessAdj=0, XmlFlag=false, oom_adj=15
I/ActivityManager( 995): Killing 4360:com.sec.android.app.controlpanel/u0a122 (adj 15): BG, 2871K, hotnessAdj=0, XmlFlag=false, oom_adj=15
I/ActivityManager( 995): Killing 12088:com.android.externalstorage/u0a10 (adj 15): BG, 10156K, hotnessAdj=0, XmlFlag=false, oom_adj=15
I/ActivityManager( 995): Killing 12103:com.google.android.gms.ui/u0a13 (adj 15): BG, 36140K, hotnessAdj=0, XmlFlag=false, oom_adj=15
I/ActivityManager_SDHA( 995): F:027M, C:194M, ProcCnt:055, avgU:-----K, mgn:073M, nF:52684K, fd:54729K, thd:143M, wm:05M, c:01, e:14, lmkIdx:15, emS:00, rsmd:T_, lstCrt:twitter.android, TOP:keramidas.TitaniumBackup, ear:0, car:0
I/ActivityManager( 995): Force stopping com.android.bluetooth appid=1002 user=0: from pid 12574
I/ActivityManager( 995): Killing 12125:com.android.bluetooth/1002 (adj -11): stop com.android.bluetooth
W/ActivityManager( 995): Scheduling restart of crashed service com.android.bluetooth/.btservice.AdapterService in 1000ms
W/ActivityManager( 995): Scheduling restart of crashed service com.android.bluetooth/.gatt.GattService in 11000ms
I/ActivityManager( 995): Force stopping service ServiceRecord{10fc555e u0 com.android.bluetooth/.btservice.AdapterService}
I/ActivityManager( 995): Force stopping service ServiceRecord{33f1dd5b u0 com.android.bluetooth/.a2dp.A2dpService}
Same problem
Hi.
I have the same problem with kenwood kdc-bt8041u receiver. I have tested with stock 5.0.1, LolliROM 3.1 and GPE edition by Danvdh. I think on GPE edition worked fine but it is 2 months since I installed LolliROM or stock in which doesn't work. I am looking for a solution too...
Any help?
I solved the problem with a factory reset.
I've a YD201 and recently upgraded from Lollipop to Marshmallow. I downloaded the stock rom and flashed it via TWRP + latest SuperSU
Wiped the dalvik cache ... ect ...
So far the upgrade went well ... but after I finished the setup-Wizard the phone keeps asking for System-Updates over and over gain.
If you check for updates the app responds: you're up-to-date no new version available ...
I stopped the manual update function, cleared the two system-update app's cache and blocked their access to the internet (via droid-wall)
Still android will ask for system-update check
On top - after an update check - the phone sometimes reboots ... when you lock the screen afterwards ...
One thing I notice is: when I use the reboot option, a message pop's up that some process tries to write in a (presumably) sqlight DB.
Unfortunately it doesn't show which process tries to write into what ...
But I suspect a coherence here between the constant update tries and a failed DB access.
Seems that the responsible app can't write it's data to the DB - get's an error and wait's for a "good chance" to reboot and try again ...
Does anyone know where Android stores the "System Update" information (eg. running Version, available version, last update try ... ect)
Yes, I already cleared the cache and did a factory reset ... no effect.
Any ideas ?
follow up
Hi all,
I was hoping on a little bit more support here ...
So I'm trying to narrow it down a bit by myself.
Code:
09-22 08:24:15.814 I/ActivityManager( 2336): START u0 {cmp=com.symphonyteleca.update/.ota.SystemUpdates} from uid 10023 on display 0
09-22 08:24:15.817 W/ActivityManager( 2336): startActivity called from non-Activity context; forcing Intent.FLAG_ACTIVITY_NEW_TASK for: Intent { flg=0x800000 cmp=com.symphonyteleca.update/.ota.SystemUpdates }
09-22 08:24:15.818 V/ActivityManager( 2336): setFocusedStack: ActivityStack{854dd9 stackId=2, 4 tasks}
09-22 08:24:15.818 V/WindowManager( 2336): setFocusedDisplay: 0
09-22 08:24:15.855 V/ActivityManager( 2336): setFocusedStack: ActivityStack{854dd9 stackId=2, 5 tasks}
09-22 08:24:15.855 V/WindowManager( 2336): setFocusedDisplay: 0
09-22 08:24:15.942 D/WifiService( 2336): New client listening to asynchronous messages
09-22 08:24:16.071 I/ActivityManager( 2336): Start proc 18926:com.yotadevices.yotaphone2.settings/1000 for broadcast com.yotadevices.yotaphone2.settings/.system_update.SystemUpdateReceiver
09-22 08:24:16.286 I/ActivityManager( 2336): Displayed com.symphonyteleca.update/.ota.SystemUpdates: +384ms
09-22 08:24:16.547 D/com.android.server.EpdUpdateParamsManager( 2336): sCurrentUpdateId: 292
09-22 08:24:16.547 D/WindowManager( 2336): Saved EpdUpdateParams for updateId 292: |0|0|0|0|0|0|255|0|false|false|false|null|; win: Window{5f699e3 u0 StatusBar EPD screen}
09-22 08:24:16.575 D/com.android.server.EpdUpdateParamsManager( 2336): Read EpdUpdateParams for updateId 292: |0|1|0|0|0|0|255|0|false|false|false|null|; win: Window{5f699e3 u0 StatusBar EPD screen}
09-22 08:24:17.570 D/com.android.server.EpdUpdateParamsManager( 2336): sCurrentUpdateId: 293
09-22 08:24:17.570 D/WindowManager( 2336): Saved EpdUpdateParams for updateId 293: |0|0|0|0|0|0|255|0|false|false|false|null|; win: Window{5f699e3 u0 StatusBar EPD screen}
09-22 08:24:17.586 D/com.android.server.EpdUpdateParamsManager( 2336): Read EpdUpdateParams for updateId 293: |0|1|0|0|0|0|255|0|false|false|false|null|; win: Window{5f699e3 u0 StatusBar EPD screen}
09-22 08:24:17.641 D/WifiService( 2336): acquireWifiLockLocked: WifiLock{com.symphonyteleca.update.ota.a type=3 [email protected]}
09-22 08:24:17.693 D/com.android.server.EpdUpdateParamsManager( 2336): sCurrentUpdateId: 294
So the Activity Manager calls the: system_update.SystemUpdateReceiver ... and then some "magic" happens ... well, there's little trace on what's happening here at all, but I suspect that the EpdUpdateParamsManager receives some data and writes it "somewhere".
Now, this "somewhere" is what I'm trying to find, and I was hoping someone can point me there ... or at least in the right direction ...
Also, EpdUpdateParams is called quite often ... but I couldn't find any documentation on it ?
Can somebody shed some light on this ?
Hm, seems that on a Yotaphone2 the System-Update is related to com.symphonyteleca.update
So I checked the DB in /data/data/com.symphonyteleca.update/databases/updates.de
But the DB appears to be empty !
I have passed my IMEI to yotaphone and the update message is gone, the phone reboots however still reboots now and then , not really clear why or what exact triggers it.
Yotaphone support is not really helping, asking " describe in details the scenario in which rebooting appears" for ex.. right...